• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 551 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.

LAUNCHXL-CC26X2R1: OAD Production Image

GOHM ELECTRONICS
Expert 2085 points
Part Number: LAUNCHXL-CC26X2R1


Hi,

We just follow http://dev.ti.com/tirex/explore/node?node=AIixxGE2y6tnPJ7cm65SFQ__pTTHBmu__LATEST document. In Task 5 there are instructions to make a so-called 'Production Image'. Since we use Ubuntu as a base OS we created a production image this way:

srec_cat ~/Desktop/workspaces/cc26x2_oad/cc26x2r1lp_bim_onchip/Debug/cc26x2r1lp_bim_onchip.hex -intel ~/Desktop/workspaces/cc26x2_oad/simple_peripheral_oad_onchip_app_CC26X2R1_LAUNCHXL_tirtos_ccs/Debug/simple_peripheral_oad_onchip_app_CC26X2R1_LAUNCHXL_tirtos_ccs_Debug_oad.bin  -bin -o simple_peripheral_oad_onchip_production.hex -intel

and in terminal we observed the following:

Since we use on-chip OAD, as stated in http://dev.ti.com/tirex/explore/node?node=AOimuSWjap.4RuDbcp7OqA__pTTHBmu__LATEST, we suppose that we should use persistent project along with the app and the bim projects, but we forgot to do so and we noticed that OAD doesn't work. It is not straightforward how to merge these three files, because the order of merging is not clear as it was in the documentation. How should we merge these three outputs?

Besides, we have one more question: is it memory efficient to use 'Production Image'?

Best regards

  • 0
    TI__Guru* 82341 points

    Hi,

    1) If you want to merge the images I think you need to use a utility such as intelhex

    2) When using on-chip OAD you need a persistent app or your device will not work after the first OAD.

    3) You can program all three images on the device, you don't necessarily have to merge them first.

    4) From a memory point of view you will notice that the "release" build configuration is more memory efficient than the "debug" build configuration. Other OAD settings don't much affect the code size.

  • 0 in reply to Marie H
    Expert 2085 points

    Hi Marie,

    By using SRecord we generated a production image like this:

    srec_cat ~/Desktop/workspaces/cc26x2_oad/cc26x2r1lp_bim_onchip/Debug/cc26x2r1lp_bim_onchip.hex -intel ~/Desktop/workspaces/cc26x2_oad/simple_peripheral_oad_onchip_app_CC26X2R1_LAUNCHXL_tirtos_ccs/Debug/simple_peripheral_oad_onchip_app_CC26X2R1_LAUNCHXL_tirtos_ccs_Debug_oad.bin -bin ~/Desktop/workspaces/cc26x2_oad/ble5_simple_peripheral_oad_onchip_cc26x2r1lp_persistent_app/FlashROM_Debug/ble5_simple_peripheral_oad_onchip_cc26x2r1lp_persistent_app_FlashROM_Debug.hex -intel -o simple_peripheral_oad_onchip_production.hex -intel

    We tested it and it looks like everything works fine.

    Best regards