SPRUI33H November 2015 – June 2024 TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1
Since error detection and correction logic is part of safety critical logic, safety applications may need to ensure that the logic is always working fine (during run time also). To enable this, a test mode is provided, in which a user can modify the data bits (without modifying the ECC/Parity bits) or ECC/Parity bits directly. Using this feature, an ECC/Parity error could be injected into data.
The memory map for ECC/Parity bits and data bits are the same. The user must choose a different test mode to access ECC/Parity bits. In test mode, all access to memories (data as well as ECC/Parity) should be done as 32-bit access only.
Table 3-14 and Table 3-15 shows the bit mapping for the ECC/Parity bits when they are read in RAMTEST mode using their respective addresses.
Data Bits Location in Read Data | Content (ECC Memory) |
---|---|
6:0 | ECC Code for lower 16 bits of data |
7 | Not Used |
14:8 | ECC Code for upper 16 bits of data |
15 | Not Used |
22:16 | ECC Code for address |
31:23 | Not Used |
Data Bits Location in Read Data | Content (Parity Memory) |
---|---|
0 | Parity for lower 16 bits of data |
7:1 | Not Used |
8 | Parity for upper 16 bits of data |
15:9 | Not Used |
16 | Parity for address |
31:17 | Not Used |