SWRU622A August   2024  – September 2024 AWRL1432 , AWRL6432 , IWRL1432 , IWRL6432 , IWRL6432AOP

 

  1.   1
  2.   Trademarks
  3. 1Introduction
  4. 2Basic Bootloader Flow
    1. 2.1 Programming Serial Data Flash Over UART (Bootloader Service)
    2. 2.2 Binary File Format
    3. 2.3 Flash Programming Sequence
    4. 2.4 Supported UART Commands/Response and Format
    5. 2.5 Flashing Sequence
    6. 2.6 ROM-Assisted Image Download Sequence
    7. 2.7 Booting Application Image
      1. 2.7.1 Booting From Serial Flash
      2. 2.7.2 Bootmode – SPI
      3. 2.7.3 Bootmode - UART
  5. 3Secondary Bootloader
    1. 3.1 SBL Execution Flow
      1. 3.1.1 Flash Memory Partitioning for SBL Execution
      2. 3.1.2 SBL Feature Modifications
      3. 3.1.3 SBL Development Considerations
  6. 4Warm Reset
    1. 4.1 Integrity Verification
    2. 4.2 LSTC/PBIST
    3. 4.3 Watchdog Timer
    4. 4.4 Reset-Triggered Flash Reload of Application
      1. 4.4.1 Hardware Solutions
        1. 4.4.1.1 PMIC I2C Messaging
        2. 4.4.1.2 External Watchdog Timer
        3. 4.4.1.3 External Voltage Monitoring or Voltage Supervisors
      2. 4.4.2 Software Solutions
        1. 4.4.2.1 Setting Boot Vector to 0x0
  7. 5Relevant Registers
    1. 5.1 Reset Registers
    2. 5.2 PC Registers
      1. 5.2.1 Addresses
  8. 6Revision History

3.1 SBL Execution Flow

The SBL execution flow is as follows:

  • The SBL application is loaded from partition 1 of SFLASH by the TI RBL

    During the execution of the SBL, it provides the user a configurable amount of time to interrupt the auto-boot process

    • The user can send the main application over a serial interface, and the SBL stores the application into the correct section of FLASH (see Flash Memory Partitioning for SBL Execution)
      • The SBL example can be found in the MMWAVE-L-SDK (for UART) and in the Radar Toolbox (for CAN/LIN)
    • Once it is flashed, the device attempts to boot the application code from FLASH and loads it into RAM, performing validity checks on the image during this process
  • If the configurable timer countdown expires, the SBL auto-boots the image in partition, and if it is invalid, it auto-boots the back-up image stored in partition 4 of SFLASH (which is flashed along with the SBL)
    • The device performs validity checks on the image during the process
  • If this boot is successful, the SBL updates the program counter and jump to the application that was loaded into RAM