SPRUJB3 March 2024 AM67 , AM67A , TDA4AEN-Q1 , TDA4VEN-Q1
Table 5-43 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 | |
ARM/Thumb | 0 | ARM mode |
1 | Thumb mode |
These boot modes are useful for debugging purposes to preclude the execution of the ROM.
During the Development boot (BOOTMODE[7] = 0), the SMS M4F ROM code will act as if boot of the primary image has completed, and the SMS M4F ROM then will be waiting for a firmware load message from DM R5. Thus the user can load a standard u-boot/SPL image to the DM R5 RAM. U-boot/SPL will then load the SMS firmware and complete the full boot.
In No-boot (BOOTMODE[7] = 1), both the SMS M4F and DM 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.