SPRS439Q June 2007 – August 2022 TMS320F28232 , TMS320F28232-Q1 , TMS320F28234 , TMS320F28234-Q1 , TMS320F28235 , TMS320F28235-Q1 , TMS320F28332 , TMS320F28333 , TMS320F28334 , TMS320F28335 , TMS320F28335-Q1
PRODUCTION DATA
Refer to the PDF data sheet for device specific package drawings
In Figure 8-23 to Figure 8-25, the following apply:
ADDRESS RANGE | PROGRAM AND DATA SPACE |
---|---|
0x30 0000 - 0x30 7FFF | Sector H (32K × 16) |
0x30 8000 - 0x30 FFFF | Sector G (32K × 16) |
0x31 0000 - 0x31 7FFF | Sector F (32K × 16) |
0x31 8000 - 0x31 FFFF | Sector E (32K × 16) |
0x32 0000 - 0x32 7FFF | Sector D (32K × 16) |
0x32 8000 - 0x32 FFFF | Sector C (32K × 16) |
0x33 0000 - 0x33 7FFF | Sector B (32K × 16) |
0x33 8000 - 0x33 FF7F | Sector A (32K × 16) |
0x33 FF80 - 0x33 FFF5 | Program to 0x0000 when using the Code Security Module |
0x33 FFF6 - 0x33 FFF7 | Boot-to-Flash Entry Point (program branch instruction here) |
0x33 FFF8 - 0x33 FFFF | Security Password (128-Bit) (Do Not Program to all zeros) |
ADDRESS RANGE | PROGRAM AND DATA SPACE |
---|---|
0x32 0000 - 0x32 3FFF | Sector H (16K × 16) |
0x32 4000 - 0x32 7FFF | Sector G (16K × 16) |
0x32 8000 - 0x32 BFFF | Sector F (16K × 16) |
0x32 C000 - 0x32 FFFF | Sector E (16K × 16) |
0x33 0000 - 0x33 3FFF | Sector D (16K × 16) |
0x33 4000 - 0x33 7FFFF | Sector C (16K × 16) |
0x33 8000 - 0x33 BFFF | Sector B (16K × 16) |
0x33 C000 - 0x33 FF7F | Sector A (16K × 16) |
0x33 FF80 - 0x33 FFF5 | Program to 0x0000 when using the Code Security Module |
0x33 FFF6 - 0x33 FFF7 | Boot-to-Flash Entry Point (program branch instruction here) |
0x33 FFF8 - 0x33 FFFF | Security Password (128-Bit) (Do Not Program to all zeros) |
ADDRESS RANGE | PROGRAM AND DATA SPACE |
---|---|
0x33 0000 - 0x33 3FFF | Sector D (16K × 16) |
0x33 4000 - 0x33 7FFFF | Sector C (16K × 16) |
0x33 8000 - 0x33 BFFF | Sector B (16K × 16) |
0x33 C000 - 0x33 FF7F | Sector A (16K × 16) |
0x33 FF80 - 0x33 FFF5 | Program to 0x0000 when using the Code Security Module |
0x33 FFF6 - 0x33 FFF7 | Boot-to-Flash Entry Point (program branch instruction here) |
0x33 FFF8 - 0x33 FFFF | Security Password (128-Bit) (Do Not Program to all zeros) |
Table 8-25 shows how to handle these memory locations.
ADDRESS | FLASH | |
---|---|---|
CODE SECURITY ENABLED | CODE SECURITY DISABLED | |
0x33FF80 – 0x33FFEF | Fill with 0x0000 | Application code and data |
0x33FFF0 – 0x33FFF5 | Reserved for data only |
Peripheral Frame 1, Peripheral Frame 2, and Peripheral Frame 3 are grouped together to enable these blocks to be write/read peripheral block protected. The protected mode ensures that all accesses to these blocks happen as written. Because of the C28x pipeline, a write immediately followed by a read, to different memory locations, will appear in reverse order on the memory bus of the CPU. This can cause problems in certain peripheral applications where the user expected the write to occur first (as written). The C28x CPU supports a block protection mode where a region of memory can be protected so as to make sure that operations occur as written (the penalty is extra cycles are added to align the operations). This mode is programmable and by default, it will protect the selected zones.
The wait states for the various spaces in the memory map area are listed in the following Wait States table.
AREA | WAIT STATES (CPU) | WAIT STATES (DMA)(1) | COMMENTS |
---|---|---|---|
M0 and M1 SARAMs | 0-wait | Fixed | |
Peripheral Frame 0 | 0-wait (writes) | 0-wait (reads) | |
1-wait (reads) | No access (writes) | ||
Peripheral Frame 3 | 0-wait (writes) | 0-wait (writes) | Assumes no conflicts between CPU and DMA. |
2-wait (reads) | 1-wait (reads) | ||
Peripheral Frame 1 | 0-wait (writes) | No access | Cycles can be extended by peripheral generated ready. |
2-wait (reads) | Consecutive (back-to-back) writes to Peripheral Frame 1 registers will experience a 1-cycle pipeline hit (1-cycle delay) | ||
Peripheral Frame 2 | 0-wait (writes) | No access | Fixed. Cycles cannot be extended by the peripheral. |
2-wait (reads) | |||
L0 SARAM | 0-wait | No access | Assumes no CPU conflicts |
L1 SARAM | |||
L2 SARAM | |||
L3 SARAM | |||
L4 SARAM | 0-wait data (reads) | 0-wait | Assumes no conflicts between CPU and DMA. |
L5 SARAM | 0-wait data (writes) | ||
L6 SARAM | 1-wait program (reads) | ||
L7 SARAM | 1-wait program (writes) | ||
XINTF | Programmable | Programmable | Programmed through the XTIMING registers or extendable through external XREADY signal to meet system timing requirements. |
1-wait is minimum wait states allowed on external waveforms for both reads and writes on XINTF. | |||
0-wait minimum writes with write buffer enabled | 0-wait minimum writes with write buffer enabled | 0-wait minimum for writes assumes write
buffer enabled and not full. Assumes no conflicts between CPU and DMA. When DMA and CPU try simultaneously (conflict), a 1-cycle delay is added for arbitration. | |
OTP | Programmable | No access | Programmed via the Flash registers. |
1-wait minimum | 1-wait is minimum number of wait states allowed. 1-wait-state operation is possible at a reduced CPU frequency. | ||
FLASH | Programmable | No access | Programmed via the Flash registers. |
1-wait Paged min | 0-wait minimum for paged access is not allowed | ||
1-wait Random min Random ≥ Paged | |||
FLASH Password | 16-wait fixed | No access | Wait states of password locations are fixed. |
Boot-ROM | 1-wait | No access | 0-wait speed is not possible. |