• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 846 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.

CC2650 OAD - Post Build Hex2Bin script

Anthony Green
Prodigy 90 points

Other Parts Discussed in Thread: CC2650

I have imported the cc2650 SimpleBLEPeripheral project and updated the build option to ext Flash OAD.  This builds OK and I can flash the hex file to the Launchpad and it runs OK.  In order to update OTA with the BLE Device Monitor, The wiki suggest that we need to add the following lines to create a bin file:

"${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin" "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin" "${CG_TOOL_ROOT}/bin/armofd” "${CG_TOOL_ROOT}/bin/armhex" "${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin"

I  have appended this line to the post-build steps and clicked OK, however when I re-enter the project settings this line has disappeared!  I assume there is an error but can't spot the issue.

Can anyone help?

Kind Regards

Tony

  • 0
    TI__Guru**** 173310 points

    Anthony Green said:
    I  have appended this line to the post-build steps and clicked OK, however when I re-enter the project settings this line has disappeared!  I assume there is an error but can't spot the issue.

    Which version of CCS are you using? If older than CCS 6.1.3, perhaps you are hitting the bug mentioned in this post?

  • 0 in reply to AartiG
    Prodigy 90 points
    I am using Version: 6.1.3.00033 . I updated after I found the issue.

    I have managed to get it to work. If the appended lines are cut and pasted directly from the wiki, it will not work. If it is typed in directly then in works ok. There appears to be some incompatibility with the character encoding from the wiki?
  • 0 in reply to Anthony Green
    TI__Guru**** 173310 points

    Anthony Green said:
    There appears to be some incompatibility with the character encoding from the wiki?

    Yes that could be it. Glad to hear you have it working now.