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
2.4.2.1.3 Examples Using I2C

The following considerations apply when using I2C with BSL-based protocol:

  • The host always starts a transfer (R or W).
  • The packet must contain the address of the slave device. All other addresses will be ignored.
  • If the slave device is not ready to process the data or send a response, it will hold the clock low (known in I2C as "stretching the clock")
  • Note that different commands have different processing times
  • Example: Host reads version from the MCU
    S0x40WA0x80A0x01A0x19A0xE8A0x62AP
    AddrHeaderLengthTX_ VERSIONChecksum _LChecksum _H
    S0x40RA0xA0/AP
    AddrVersion
  • Example: Host writes 16 bytes to address 0xC000.
    S0x40WA0x80A0x14A0x10A0x00A0xC0A0x00A0x03A0xEEA
    AddrHeaderLengthRX_DATA_ BLOCKAddrLAddrMAddrHData0Data1
    0x47A0xFFA0xB2A0x40A0x80A0x5AA0x20A0x01A0xD2A
    Data2Data3Data4Data5Data6Data7Data8Data9Data10
    0xD3A0x22A0x00A0xD2A0xD3A0x15A0xE4AP
    Data11Data12Data13Data14Data15Checksum _LChecksum _H
    S0x40RA0x00/AP
    AddrOK