• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 120 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

LAUNCHXL-CC26X2R1: SDK Change / Update

LAUNCHXL-CC26X2R1: Update to new SDK loses all stored bonding information

SPEEDBIRD
Intellectual 721 points
Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: UNIFLASH

Good Morning everybody!

I have noticed an issue when updating our CC26X2R1 firmware from the simplelink_cc13x2_26x2_sdk_3_20_00_68 to the simplelink_cc13xx_cc26xx_sdk_5_40_00_40 SDK.

Every time I update the CC26X2R from the "old" SDK Application firmware to the "new" SDK Application firmware, it seems like all the stored bonding information gets deleted and the CC26X2R1 needs to be "rebonded" with every device. 

Note, this only happens when updating from the old SDK to the new one. Updates within the old or new SDK work like a charm and I don't lose any stored bonding information.
I have never experienced this behavior before.
Is this an expected behavior?
How can I solve this issue?

Thanks in advance!

SPEEDBIRD

  • 0
    TI__Mastermind 30309 points

    Hi SPEEDBIRD,

    Are you using a custom example or are you able to see this when bonding using one of the default examples and then updating to the equivalent example on the newer SDK? How are you flashing the device? Can you provide the console logs generated when flashing from an old SDK to a new one and when flashing between the same SDKs?

    Best Regards,

    Jan

  • 0 in reply to Jan
    Intellectual 721 points

    Hi Jan,

    I'm using the multi_role project. The update is done via OAD and not uniFlash / CCS. 

    This only happens when updating from simplelink_cc13x2_26x2_sdk_3_20_00_68 to the simplelink_cc13xx_cc26xx_sdk_5_40_00_40 SDK. When I update to a new application firmware within the simplelink_cc13xx_cc26xx or simplelink_cc13x2_26x2_sdk_3_20_00_68 SDK the bonding information is not deleted (as expected).

    Regards,

    SPEEDBIRD

  • 0 in reply to SPEEDBIRD
    TI__Mastermind 30309 points

    Hi SPEEDBIRD,

    Got it. Thanks for the additional information. Are you making use of the OAD Control Point Characteristic? This characteristic can be used to erase all bonds if a specific value is written to it. Can you read through this E2E thread as well as the E2E thread linked within and let me know if this seems to be the same issue you are observing?

    Best Regards,

    Jan