SPRUII0F May 2019 – June 2024 TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S
The purpose of this chapter is to explain the boot read-only memory (ROM) code functionality for CPU1, CPU2, and CM cores, including the boot procedure. It also discusses the functions and features of the boot ROM code, and provides details about the ROM memory map contents. On every reset, the device executes a boot sequence in the ROM depending on the reset type and boot configuration. This sequence will initialize the device to run the application code. For CPU1, the boot ROM also contains peripheral bootloaders which can be used to load an application into RAM. These bootloaders can be disabled for safety or security purposes.
Refer to Table 5-1 for details on available boot features across CPU1, CPU2, and CM. Additionally, Table 5-2 shows the sizes of the various ROMs on the device.
Boot Feature | CPU1 (Master) | CPU2 | CM |
---|---|---|---|
Initiate boot process | Device Reset | CPU1 Application | CPU1 Application |
Boot mode selection | GPIOs | IPC Register | IPC Register |
Supported boot modes:
|
Yes | Yes | Yes |
Boot to User OTP | No | Yes | Yes |
Copy from IPC Message RAM and boot to RAM | No | Yes | Yes |
Peripheral boot loader support | Yes | No | No |
ROM | CPU1 Size | CPU2 Size | CM Size |
---|---|---|---|
Unsecure boot ROM | 192 KB | 64 KB | 64 KB |
Secure ROM | 64 KB | 64 KB | 32 KB |
CLA data ROM | 8 KB | 8 KB | N/A |