• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 792 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.

CCS/MSP430F2417: .Bin file creation for MSP430 in CCS 9.2 v

Parama Sivan
Prodigy 60 points
Part Number: MSP430F2417

Tool/software: Code Composer Studio

Hi,

I couldn't find the correct way to generate the .bin file from the intel .hex format or .out file.  I have tried the following way in my project settings, but it throws error during compilations. Kindly help to fix the bug

Found in the document:

For example, to convert the executable (.out) to binary format (.bin), the following command can be used as post-build step:

“${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin” “${BuildArtifactFileName}” “${BuildArtifactFileBaseName}.bin” “${CG_TOOL_ROOT}/bin/ofd2000” “${CG_TOOL_ROOT}/bin/hex2000” “${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin”

Be sure to replace ofd2000 and hex2000 with the respective binaries for your device, for example, ofd6x and hex6x (for c6000) or armofd and armhex (for ARM).

Error

“C:/ti/ccs910/ccs/utils/tiobj2bin/tiobj2bin� “DGSI_11000.out� “DGSI_11000.bin� “C:/ti/ccs910/ccs/tools/compiler/ti-cgt-msp430_18.12.3.LTS/bin/ armofd� “C:/ti/ccs910/ccs/tools/compiler/ti-cgt-msp430_18.12.3.LTS/bin/armhex� “C:/ti/ccs910/ccs/utils/tiobj2bin/mkhex4bin�
makefile:199: recipe for target 'post-build' failed
process_begin: CreateProcess(NULL, “C:/ti/ccs910/ccs/utils/tiobj2bin/tiobj2bin� “DGSI_11000.out� “DGSI_11000.bin� “C:/ti/ccs910/ccs/tools/compiler/ti-cgt-msp430_18.12.3.LTS/bin/ armofd� “C:/ti/ccs910/ccs/tools/compiler/ti-cgt-msp430_18.12.3.LTS/bin/armhex� “C:/ti/ccs910/ccs/utils/tiobj2bin/mkhex4bin�, ...) failed.

Thanks,

Param.

  • 0
    TI__Guru**** 168367 points

    Param, 

    I am not sure if this is an artifact of the Copy+Paste to the e2e post or your error message actually shows all these special characters. If you have special characters on the path, keep in mind that certain utilities of CCS have issues with it. 

    At any rate, the names of the utilities shouldn't have the arm prefix (armofd, armhex, etc.) but instead have the 430 suffix (ofd430, hex430, etc.). That would fail in all scenarios. 

    Hope this helps,

    Rafael