• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 51 subscribers
  • Views 1047 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: Loading modified version of Project Zero

eteom
Intellectual 370 points
Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: UNIFLASH

First loaded Project Zero code on to LAUNCHPAD-cc26x2 using Uniflash, made some modifications to the code (release build). Tried loading the modified code using .hex file generated.But the code on board did not change.

Among the changes to Project Zero from example code was change to advertising data which should allow to easily identify whether code changed or not. 

The code previously on the board was multi_role for which using hex file to update code works fine. 

Also the following error occurs when loading Project Zero changes, although the code gets loaded. This did not happen in case of multi_role code. Is that error expected or caused by some mistake I made while loading code?

Okay in addition to this OAD bin file is not getting generated with following error though the hex file gets generated.

  • 0
    TI__Intellectual 1040 points
    The OAD BIM project locks a section of the configuration, which is why you see the error when trying to reprogram the board. On the left side navigation bar select Settings and Utilities -> Erase Entire Flash before reloading the binary (this will also require you to reflash the BIM).

    For the second part of your question, first verify that the oad_image_tool is in the location specified. Then check the post build options by right clicking on the project in CCS then Properties -> Build -> Steps. From there verify that the correct file path syntax is being used and correct build location.
  • 0 in reply to AJB
    Intellectual 370 points

    The oad_image_tool is in the path specified, as for the post build options it seems okay, attached it below:

    sdk used: SimpleLink CC26x2 2.20.00.36, mentioning this since when i started out i was using SimpleLink CC26x2 2.10.00.44 an oad.bin file was generated although moved on from that sdk and the download link has been updated to CC26x2 2.20.00.36 sdk. 

  • 0 in reply to eteom
    TI__Intellectual 1040 points
    The OAD image tool can be ran from any terminal. Please try this to make sure the tool can be executed this way then try adding it as a post build step.
  • 0 in reply to AJB
    Intellectual 370 points
    Well the issue with the OAD file generation is solved. The file path was correct, but the oad_image_tool.exe for windows was not there in the CC26x2 2.20.00.36 sdk, that's why it worked with earlier CC26x2 2.10.00.44 sdk. It was my bad i assumed the oad_image_tool.py was a script which runs the .exe from the bin folder, but when you asked to run it from command line, that's when I noticed the windows oad_tool.exe was missing. I copied the oad_tool.exe from the other sdk and now it works.
    Well with that out of the way back to the original question, modified code isn't getting updated when loading the hex file, but when loading the OAD file it gets updated, is that supposed to be how its done for projects with off-chip OAD support?
  • 0 in reply to eteom
    TI__Intellectual 1040 points
    The code should be updated regardless. It may depend on the setting you have while flashing. From Settings & Utilities -> Erase there are settings specifying how to flash the device. Try changing the setting to All Unprotected Sectors then flashing the hex. The settings is defaulted to retain any content in the unprotected sectors and that may be why.