• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 51 subscribers
  • Views 634 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2640R2F: enable OTA and SBL.

Netanel Unger
Expert 1190 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: UNIFLASH

OTA - over the air update. SBL - download image to chip via uart.

When program the chip with OTA, i'm downloading to the chip the BIM (boot manager) and the application BIN with uniflash app.

When i'm programming the chip via SBL, i'm using .bin file that IAR build, the .bin contain only the application code without the BIM.

how can i create .bin file for SBL, that include the BIM and the application in one file?

  • 0
    TI__Mastermind 33460 points
    Hello,

    If I understand correctly, you are trying to combine BIM and your application into a single .bin file with all necessary headers attached.
    We cover this in the final task (Task 4) of the Enhanced OAD SimpleLink Academy here: dev.ti.com/.../

    In the example we create a hex file for output, but srecord also supports output type as binary. Just be sure to use hex for the BIM so the start address is known.
  • 0 in reply to Sean2
    Expert 1190 points

    Thanks !!!!

    good to know that so much information already available, it's just so hard to find it :)

  • 0 in reply to Sean2
    Expert 1190 points

    Before I added the OTA and the BIM the chip entered bootloader and i uploaded image via UART.

    But now, the chip does not start the bootloader. 

    Can it be because the bootloader settings (register data) need to be set when the BIM starts?

    Can you explain to be how to do it?

    All the bootloader define has been changed:

    //#####################################
// Bootloader settings
//#####################################

#ifndef SET_CCFG_BL_CONFIG_BOOTLOADER_ENABLE
//#define SET_CCFG_BL_CONFIG_BOOTLOADER_ENABLE            0x00       // Disable ROM boot loader
#define SET_CCFG_BL_CONFIG_BOOTLOADER_ENABLE         0xC5       // Enable ROM boot loader
#endif

#ifndef SET_CCFG_BL_CONFIG_BL_LEVEL
#define SET_CCFG_BL_CONFIG_BL_LEVEL                  0x0        // Active low to open boot loader backdoor
//#define SET_CCFG_BL_CONFIG_BL_LEVEL                     0x1        // Active high to open boot loader backdoor
#endif

#ifndef SET_CCFG_BL_CONFIG_BL_PIN_NUMBER
#define SET_CCFG_BL_CONFIG_BL_PIN_NUMBER                11       // DIO number for boot loader backdoor
#endif

#ifndef SET_CCFG_BL_CONFIG_BL_ENABLE
#define SET_CCFG_BL_CONFIG_BL_ENABLE                 0xC5        // Enabled boot loader backdoor
//#define SET_CCFG_BL_CONFIG_BL_ENABLE                    0xFF       // Disabled boot loader backdoor
#endif

  • 0 in reply to Netanel Unger
    TI__Mastermind 33460 points
    Hi,

    In the OAD case the BIM is responsible for linking the CCFG. When you added the OTA support did you migrate your CCFG settings to the BIM?

    Note that BIM does require #define SET_CCFG_IMAGE_VALID_CONF_IMAGE_VALID 0x1F000 so be sure to merge this with you BL settings.