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: any potential problem if updating code from old SDK version into latest version via OAD ?

Part Number: CC2640R2F
Other Parts Discussed in Thread: BLE-STACK

Hi TI, 

  • BLE Stack : “simplelink_cc2640r2_sdk_1_35_00_33”
  • Example   : “simplelink_cc2640r2_sdk_ble_example_pack_1_35_00_36”

 

As per understanding, the memory structure is as below, (please correct me if wrong),

  • ROM code:   contains RTOS kernel and most of BLE Stack software.
  • Flash code:
    • Bootloader.
    • BLE Protocol Stack (include: Library portion).
    • TI RTOS & Peripheral drivers.
    • Application & Profiles.

 

Customer developed hid_adv_remote SW based on old version CC2640R2_SDK v1.35.

Now, plan to update the code using (migration based on) latest CC2640R2_SDK v3.20, via OAD (= Over-the-Air Download).

Understand that latest SDK v3.2 structure is totally different compare to old v.1.35.

Questions:

  [For the (CC2640R2F) ROM code portion ]:

   1)  is there any BLE Stack update (via ROM patches) so far ? 

        If yes, will there any issues after SW upgrade via OAD ?

  [ For the (CC2640R2F) Flash code portion ]:

    2)  is it possible to update the whole Flash code portion (include the BLE Stack library, but minus Bootloader) ?   any concern / issue ?

 

Thank you in advance.

  • Hi,

    I do not think you can fit the SDKv3.20 based HID application on the CC2640R2, although that is up to you to assess. you will need to update both app and stack so you do not have to consider any ROM patching as it will be part of the BLE-Stack portion. 

  • Hi Joakim,

    What do you mean with "I do not think you can fit the SDKv3.20 based HID application on the CC2640R2,... ." ?

    Is it because of code size issue ?   or Bootloader compatibility issue ?   or BLE stack compatibility issue (from old version v1.35 to new version v3.20) ?   or BLE version (v4.2 - v5.x) issue ?   or because of other reasons ?

    Thanks \ William

  • Hi,

    Purely based on the fact that HID consumes significant memory and the BLE-Stack memory usage has increased throughout the many updates since v1.35.

  • Hi Joakim,

    In another new project, customer managed to develop hid_adv_remote (migration from CC2640R2F SDK v1.35 to) using SDK v3.20, so far did not encountered memory usage issue.

    For those end-products already shipped to end-customer (which is based on SDK v1.35), will need to update the the code via OAD. The question is :

    • whether can use OAD to upgrade the remote's code to new SDK v3.20 based code ?   is there any potential risks ?
    • does the (SDK v1.35) Bootloader code called APIs will be different / changed in new SDK v3.20) ?
    • any other concerns ?

    Thank you.

  • Hi,

    William T said:
    • whether can use OAD to upgrade the remote's code to new SDK v3.20 based code ?   is there any potential risks ?

    Yes, disregarding the memory constraints, no problem.

    William T said:
    • does the (SDK v1.35) Bootloader code called APIs will be different / changed in new SDK v3.20) ?

    No, I do not thinks so.