SPRUIM2H May 2020 – October 2023 AM2431 , AM2432 , AM2434 , AM6411 , AM6412 , AM6421 , AM6422 , AM6441 , AM6442
Table 4-34 shows configuration pins assignment to functions when boot mode is the No-boot mode.
Field | Value | Description |
---|---|---|
No/Dev | 0 | Development Boot |
1 | No boot |
These boot modes are useful for debugging purposes to preclude the execution of the ROM.
During the Development boot (BOOTMODE[7] = 0), the DMSC ROM code will act as if boot of the primary image has completed, and the DMSC ROM then will be waiting for a firmware load message from MCU R5. Thus the user can load a standard u-boot/SPL image to the R5 RAM. U-boot/SPL will then load the DMSC firmware and complete the full boot.
In No-boot (BOOTMODE[7] = 1), both the DMSC and MCU R5 ROMs are bypassed and both CPUs are held in a dummy branch-to-self loop. No-boot is the most minimal device touch state by the ROM - only minimal hardware configurations are done and none of the PLLs is locked/configured. No-boot is suitable if user wants to load his own PLL, Pad config, and other basic settings.