SPRUIY4B February 2023 – May 2024 TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1
The wait mode puts the CPU in a loop in the boot ROM code and does not branch to the user application code. The device can enter the wait boot mode either through manually being set or because of some issue during boot up. Using the wait boot mode is recommended when using a debugger to avoid any JTAG issues. There is an ESTOP provided for debugging during Wait boot.
Option | BOOTDEFx Value | Watchdog Status | Package Supported |
---|---|---|---|
0 (default) | 0x04 | Enabled | All |
1 | 0x24 | Disabled | All |
During boot ROM execution, there are situations where the CPU can enter a wait loop in the code. This state can occur for a variety of reasons. Table 5-20 details the address ranges that the CPU PC register value falls between, if the CPU has entered one of these instances.
Following are the actions for entering wait boot mode:
Address Range | Description |
---|---|
0x003F BC2D – 0x003F BC35 | In Wait Boot Mode |
0x003F CF03 – 0x003F CF0B | In SCI Boot waiting on autobaud lock |
0x003F FD4C – 0x003F FDE9 | In NMI Handler |
0x003F FE18 – 0x003F FE2F | In ITRAP ISR |
0x003F C191 - 0x003F C1A8 0x003F C6F2 - 0x003F C711 |
In Parallel boot waiting for control signal |