SPRUHM8K December 2013 – May 2024 TMS320F28374D , TMS320F28375D , TMS320F28376D , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28378D , TMS320F28379D , TMS320F28379D-Q1
When connected to the device using an emulator, the EMU_BOOTCTRL control word is used to determine the boot mode. This control word allows the user to experiment with various boot mode settings before writing to the BOOTCTRL register in the user-configurable DCSM OTP. The values that can be set in the BMODE field of the EMU_BOOTCTRL control word are listed in Section 4.7. Some notable options include being able to have emulation boot read from the boot mode select pins, emulate standalone boot using the values in OTP, and boot according to the Get boot value stored in OTP memory. Refer to Section 4.10.6 for details on the GPIOs used in the various boot modes.
Key | BMODE Value | Realized Boot Mode | CPU Support |
---|---|---|---|
!= 0x5A | Don’t Care | Wait Boot | CPU1 and CPU2 |
0xFE | Boot as per BMSP0 and BMSP1 | CPU1 Only | |
0xFF | Emulate Standalone boot | CPU1 and CPU2 | |
0x00 | Parallel Boot | CPU1 and CPU2 | |
0x01 | SCI Boot 0 | CPU1 and CPU2 | |
0x02 | Wait Boot | CPU1 and CPU2 | |
0x03 | Get Mode(read OTP BOOTCTRL) | CPU1 and CPU2 | |
= 0x5A | 0x04 | SPI Boot 0 | CPU1 and CPU2 |
0x05 | I2C Boot 0 | CPU1 and CPU2 | |
0x07 | CAN Boot 0 | CPU1 and CPU2 | |
0x0A | RAM Boot | CPU1 and CPU2 | |
0x0B | Flash Boot | CPU1 and CPU2 | |
0x0C | USB Boot | CPU1 Only | |
0x81 | SCI Boot 1 | CPU1 Only | |
0x84 | SPI Boot 1 | CPU1 Only | |
0x85 | I2C Boot 1 | CPU1 Only | |
0x87 | CAN Boot 1 | CPU1 Only | |
Other | Wait Boot | CPU1 and CPU2 |