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.

CC2652R7: Same HOST_TEST binary for R1 & R7

Part Number: CC2652R7


Hi,

Can we use the host_test binary compiled for CC2652R1 in CC2652R7?

In other words, Is that possible to load same host_test.bin file for both CC2652R1 and CC2652R7 for BLE application (host test)? if so, what we should do?

Thanks

  • Hi,

    I am afraid you cannot flash a binary compiled for R1 on a R7 device.

    The right approach is rather to use the hexfile built for the CC2652R7. This file is available in the SDK in <SDK>examples\rtos\LP_CC2652R7\ble5stack\hexfiles. If this file is not available in your SDK, it means you are using a too old SDK.

    In all the cases, I strongly recommend you to use the newer SDK (6_10) and to NOT use SDK before 5_40 with CC2652R7. SDK 5_30 and before are pre-production SDK for CC2652R7.

    Best regards,

  • Thanks Clemet. 

     We have products with both chipsets (R1 and R7). So we cannot keep same firmware(bin/hex) for both R1 and R7?  

  • Hi,

    We do not recommend nor test the approach you are suggesting.

    If such approach ease your workflow, then you could give it a shot and see what happens. Once again, we do not test this approach and some differences in the radio performances should be expected.

    Alternatively, you could check the chipset used before flashing the device. Based on that, you could then select the proper binary. Please let me know if you need more guidance here.

    Thank you for your comprehension.

    Best regards,

  • Thanks Clemnet.

    1) What would be the best way to check the chipset to find the the version R1/R7?

    2) For CC2652R1, we do have this change to enable bootloader with backdoor. Do we need to so the same for R7 chip?

    --- a/simplelink_cc13xx_cc26xx_sdk_5_30_01_01/source/ti/devices/cc13x2_cc26x2/startup_files/ccfg.c
    +++ b/simplelink_cc13xx_cc26xx_sdk_5_30_01_01/source/ti/devices/cc13x2_cc26x2/startup_files/ccfg.c
    @@ -222,22 +222,22 @@
    //#####################################

    #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
    +//#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
    +#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 0xFF // DIO number for boot loader backdoor
    +#define SET_CCFG_BL_CONFIG_BL_PIN_NUMBER 0x0B // 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
    +#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

  • Hi,

    1) You could use the serial boot loader commands as described in this app note: https://www.ti.com/lit/swra466 to read the flash size of the device. 

    2) The same modification is required to enable the backdoor for the boot loader.

    I hope this will help,

    Best regards,