JAJSFH1J November 2010 – September 2021 TMS320F28062 , TMS320F28062F , TMS320F28063 , TMS320F28064 , TMS320F28065 , TMS320F28066 , TMS320F28067 , TMS320F28068F , TMS320F28068M , TMS320F28069 , TMS320F28069F , TMS320F28069M
PRODUCTION DATA
In Figure 8-1 through Figure 8-8, the following apply:
ADDRESS RANGE | PROGRAM AND DATA SPACE |
---|---|
0x3D 8000 to 0x3D BFFF | Sector H (16K × 16) |
0x3D C000 to 0x3D FFFF | Sector G (16K × 16) |
0x3E 0000 to 0x3E 3FFF | Sector F (16K × 16) |
0x3E 4000 to 0x3E 7FFF | Sector E (16K × 16) |
0x3E 8000 to 0x3E BFFF | Sector D (16K × 16) |
0x3E C000 to 0x3E FFFF | Sector C (16K × 16) |
0x3F 0000 to 0x3F 3FFF | Sector B (16K × 16) |
0x3F 4000 to 0x3F 7FF5 | Sector A (16K × 16) |
0x3F 7FF6 to 0x3F 7FF7 | Boot-to-Flash Entry Point (program branch instruction here) |
0x3F 7FF8 to 0x3F 7FFF | Security Password (128-Bit) (Do not program to all zeros) |
ADDRESS RANGE | PROGRAM AND DATA SPACE |
---|---|
0x3E 8000 to 0x3E 9FFF | Sector H (8K × 16) |
0x3E A000 to 0x3E BFFF | Sector G (8K × 16) |
0x3E C000 to 0x3E DFFF | Sector F (8K × 16) |
0x3E E000 to 0x3E FFFF | Sector E (8K × 16) |
0x3F 0000 to 0x3F 1FFF | Sector D (8K × 16) |
0x3F 2000 to 0x3F 3FFF | Sector C (8K × 16) |
0x3F 4000 to 0x3F 5FFF | Sector B (8K × 16) |
0x3F 6000 to 0x3F 7FF5 | Sector A (8K × 16) |
0x3F 7FF6 to 0x3F 7FF7 | Boot-to-Flash Entry Point (program branch instruction here) |
0x3F 7FF8 to 0x3F 7FFF | Security Password (128-Bit) (Do not program to all zeros) |
Addresses 0x3F 7FF0 to 0x3F 7FF5 are reserved for data and should not contain program code.
Peripheral Frame 1 and Peripheral Frame 2 are grouped together to enable these blocks to be write/read peripheral block protected. The protected mode makes sure that all accesses to these blocks happen as written. Because of the 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 CPU supports a block protection mode where a region of memory can be protected so that operations occur as written (the penalty is extra cycles are added to align the operations). This mode is programmable and by default, it protects the selected zones.
The wait states for the various spaces in the memory map area are listed in Table 8-5.
AREA | WAIT STATES (CPU) | COMMENTS |
---|---|---|
M0 and M1 SARAMs | 0-wait | Fixed |
Peripheral Frame 0 | 0-wait | |
Peripheral Frame 1 | 0-wait (writes) | Cycles can be extended by peripheral-generated ready. |
2-wait (reads) | Back-to-back write operations to Peripheral Frame 1 registers will incur a 1-cycle stall (1-cycle delay). | |
Peripheral Frame 2 | 0-wait (writes) | Fixed. Cycles cannot be extended by the peripheral. |
2-wait (reads) | ||
Peripheral Frame 3 | 0-wait (writes) | Assumes no conflict between CPU and CLA/DMA cycles. The wait states can be extended by peripheral-generated ready. |
2-wait (reads) | ||
L0–L8 SARAM | 0-wait data and program | Assumes no CPU conflicts |
OTP | Programmable | Programmed through the Flash registers. |
1-wait minimum | 1-wait is minimum number of wait states allowed. | |
FLASH | Programmable | Programmed through the Flash registers. |
0-wait Paged min | ||
1-wait Random min Random ≥ Paged | ||
FLASH Password | 16-wait fixed | Wait states of password locations are fixed. |
Boot-ROM | 0-wait |