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

CC1312R: Failed to generate OAD image by CCS

Yu Yu
Prodigy 120 points
Part Number: CC1312R

Hi,

The purpose is to generate OAD image file by rfWsnNodeExtFlashOadClient project from simplelink_cc13x2_26x2_sdk_4_30_00_54.

It always show below error reminder during compiling after exactly follow all steps. Which step is probable wrong?

'ommon' is not recognized as an internal or external command,
operable program or batch file.
gmake[2]: [post-build] Error 1 (ignored)

**** Build Finished ****

So I call oad image tool.exe directly via cmd to generate .bin file, it can successfully generate .bin file now. 

Is it successful to generate required OAD image now or must generate by CCS post-build? Thanks a lot.

  • 0
    TI__Guru* 83801 points

    I will have one of our OAD experts looking into this.

    BR

    Siri

  • 0
    TI__Genius 14845 points

    Hi Yu,

    You can use the OAD image generated by the OAD Image Tool when running it as a standalone application. If you use the same parameters in CCS and when using it standalone, it will produce the same image. 

    Based on the error you are getting, it seems like you are missing a "c" to point to the "common" folder which will enable CCS to reach the OAD Image Tool which is located in <SDK installation path>\tools\common\oad\oad_image_tool.py

    Thanks, 
    Elin

  • 0 in reply to Elin W
    Prodigy 120 points

    Thanks, Elin.