SPRUHM8K December 2013 – May 2024 TMS320F28374D , TMS320F28375D , TMS320F28376D , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28378D , TMS320F28379D , TMS320F28379D-Q1
The boot sequence, Table 4-3, describes the general boot ROM procedure each time the CPU core is reset. For dual-core devices, CPU1 is the master controller and controls the boot process. Each CPU goes through a boot procedure, but under the control of CPU1. The exception to this rule is when CPU2 is set to boot-to-Flash, in which CPU1 is not involved.
During booting, the boot ROM code updates a boot status location in RAM that details the actions taken during this process. Refer to Section 4.10.11 for more details.
Step | CPU1 Action | CPU2 Action |
---|---|---|
1 | After reset, the FUSE error register is checked for any errors and are handled accordingly. | Held in reset. |
2 | Clock and Flash Configuration | Held in reset. |
3 | Device configuration registers are programmed from OTP. | Held in reset. |
4 | All CPU RAMs are initialized. | Held in reset. |
5 | Any pending NMI is handled by the code. | Held in reset. |
6 | DCSM initialization sequence is executed. | Held in reset. |
7 | Bring CPU2 out of reset. | Brought out of reset and performs: 1. Clock and Flash Configuration 2. All CPU RAMs are initialized 3. DCSM initialization |
8 | Based on the boot mode select GPIO pins and boot mode set in OTP, the boot mode is determined, and the appropriate boot sequence is executed. Refer to Section 4.8 for a flow chart of the device boot sequences. | Based on the boot mode value read from OTP, the appropriate boot sequence is executed. |