SLAA721E October   2016  – March 2020 MSP430FR5969 , MSP430FR5969-SP , MSP430FR5994 , MSP430FR6989

 

  1.   Trademarks
  2. 1Introduction
    1. 1.1 Glossary
    2. 1.2 Conventions
  3. 2Implementation
    1. 2.1 Main
    2. 2.2 Application Manager
      1. 2.2.1 Bootloader and Application Detection
        1. 2.2.1.1 Forcing Bootloader Mode
        2. 2.2.1.2 Application Validation
        3. 2.2.1.3 Jumping to Application
      2. 2.2.2 Memory Assignment
      3. 2.2.3 Interrupt Vectors in FRAM Devices
    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 UART
        2. 2.4.1.2 SPI
        3. 2.4.1.3 CC110x
        4. 2.4.1.4 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 UART or CC110x
  4. 3Customization of MSP430FRBoot
    1. 3.1 Predefined Customizations
  5. 4Building MSPBoot
    1. 4.1 LaunchPad™ Development Kit Hardware
    2. 4.2 CC110x Hardware
    3. 4.3 Software
      1. 4.3.1 Building the Target Software
      2. 4.3.2 Convert Application Output Images
      3. 4.3.3 Generating Linker Files
  6. 5Demo Using FRAM LaunchPad Development Kit as Host
    1. 5.1 Hardware
    2. 5.2 Building the Host Project
    3. 5.3 Running the Demo
  7. 6Porting the target side example projects to other MSP430FR devices
  8. 7References
  9. 8Revision History

2.4.1.4 Comm Sharing

The user application can use the communication interface as desired (UART, GPIO, or other purpose), because the resources are released when the microcontroller jumps to the application. Optionally, the CI PHY-DL can be shared with the application, allowing it to use the same communication interface and reducing the application footprint. When this feature is enabled, the bootloader shares the function pointers from Table 2-3.

Table 2-3 Boot2App_Vector_Table Definition
Function PointerDescription
Boot2App_Vector_TableTable with addresses of shared CI PHY-DL functions
TI_MSPBoot_CI_PHYDL_InitFunction used to initialize PHY-DL passing a pointer to an application t_CI_Callback
TI_MSPBoot_CI_PHYDL_PollFunction checks all relevant flags and calls corresponding callbacks when required.
TI_MSPBoot_CI_PHYDL_TxByteFunction used to write the TX Buffer

The application must declare its own callbacks, which are passed during initialization of CI PHY-DL and called when the corresponding event is detected. The PHY-DL layer is designed with low footprint being a top priority. The application can always implement its own drivers if the PHY-DL implementation is inadequate. Application examples showing how to share CI PHY-DL are included in the software package.