SLAA600E June   2013  – January 2024

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 Glossary
    2. 1.2 Conventions
  5. 2Implementation
    1. 2.1 Main
    2. 2.2 Application Manager
      1. 2.2.1 Boot and Application Detection
        1. 2.2.1.1 Force Bootloader Mode
        2. 2.2.1.2 Application Validation
        3. 2.2.1.3 Jump to Application
      2. 2.2.2 Vector Redirection
      3. 2.2.3 Interrupt Vectors in Flash Devices
      4. 2.2.4 Dual Image Support
        1. 2.2.4.1 Jumping to Application in Dual Image Mode
    3. 2.3 Memory Interface (MI)
      1. 2.3.1 Dual Image Support
    4. 2.4 Communication Interface (CI)
      1. 2.4.1 Physical-DataLink (PHY-DL)
        1. 2.4.1.1 I2C
          1. 2.4.1.1.1 Time-out Detection
        2. 2.4.1.2 UART
        3. 2.4.1.3 SPI
        4. 2.4.1.4 CC110x
        5. 2.4.1.5 Comm Sharing
      2. 2.4.2 NWK-APP
        1. 2.4.2.1 BSL-Based Protocol
          1. 2.4.2.1.1 Security
          2. 2.4.2.1.2 BSL-Based Protocol using CC110x
          3. 2.4.2.1.3 Examples Using I2C
          4. 2.4.2.1.4 Examples Using UART or CC110x
  6. 3Customization of MSPBoot
    1. 3.1 Predefined Customizations
  7. 4Building MSPBoot
    1. 4.1 Starting a New Project
      1. 4.1.1 Creating a New MSPBoot Project
        1. 4.1.1.1 MSPBootProjectCreator.pl
        2. 4.1.1.2 Importing Project Spec File in CCS
        3. 4.1.1.3 Modifying Generated Source Code
          1. 4.1.1.3.1 Modifying MSPBoot Main.c
          2. 4.1.1.3.2 Modifying TI_MSPBoot_Config.h
          3. 4.1.1.3.3 Modifying TI_MSPBoot_CI_PHYDL_xxxx_xxx.c
          4. 4.1.1.3.4 Modifying TI_MSPBoot_AppMgr.c
          5. 4.1.1.3.5 Modifying Application Main.c
          6. 4.1.1.3.6 Modifying TI_MSPBoot_Mgr_Vectors_xxxx.c
      2. 4.1.2 Loading Application Code With MSPBoot
        1. 4.1.2.1 Convert Application Output Images
    2. 4.2 Examples
      1. 4.2.1 LaunchPad Development Kit Hardware
      2. 4.2.2 CC110x Hardware
      3. 4.2.3 Building the Target Project
      4. 4.2.4 Building the Host Project
      5. 4.2.5 Running the Examples
  8. 5References
  9. 6Revision History
4.1.1.3.2 Modifying TI_MSPBoot_Config.h

There are four TODO items in TI_MSPBoot_Config.h that require user modification:

  • Define the MCLK Frequency
    • After modifying main.c other portions of the code need to know the MCLK frequency to operate properly.
  • Setup Watchdog Interval
    • In some applications, there may be a need to reset the device if the bootloader becomes unresponsive. The interval length is most dependent on the size of flash for the device being programmed. The more flash space, the longer the interval must be. For example, in the MSP430F5529 that contains 128KB of flash an interval greater than 6 seconds. If using the watchdog timer, the NDEBUG define also must be uncommented.
  • Setup the Hardware Entry Condition
    • Typically a bootloader offers a way to enter the code through a hardware condition. In MSPBoot, the user can decide based on the status of a pin being high or low.
  • Uncomment Configuration Options
    • There are many different configuration options that need to be selected based on the communication interface being used. You can also find more information on this in Table 3-1.
    • When using I2C:
      • Uncomment CONFIG_CI_PHYDL_START_CALLBACK and CONFIG_CI_PHYDL_I2C_SLAVE_ADDR
    • When using UART:
      • Uncomment CONFIG_CI_PHYDL_UART_BAUDRATE
    • When using CC110x:
      • Uncomment CONFIG_CI_PHYDL_CC1101_FREQUENCY