• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1751 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.

Another "Can't create a .bin" in CCS problem

Vic Elias2
Prodigy 80 points

I've been having trouble generating a .bin file in CCS 6.1.0 for a Tiva TM4C1231H6PZI, no RTOS.

I've tried all the command lines that people have posted here and in the TI documents (they are all the same) and put them on one single line in the Post-Build steps window with no luck.

All the utility files called in that line exist in the proper directories on my machine.

I look in my debug directory where the build and the newly generated .out file is placed and no .bin.

What am I doing wrong?

Here is the console output fragment from CCS:

<Linking>
'Finished building target: RDAC V2.out'
' '
'Generate BIN'
"C:/ti/ccsv6/utils/tiobj2bin/tiobj2bin" "RDAC V2.out" "RDAC V2.bin" "C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.2/bin/armofd" "C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.2/bin/armhex" "C:/ti/ccsv6/utils/tiobj2bin/mkhex4bin"
' '
'Invoking: ARM Hex Utility'
"C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.2/bin/armhex" -o "RDAC V2.hex" "RDAC V2.out"
Translating to Extended Tektronix format...
warning: section RDAC V2.out(.text) was padded by 2 to a size of 75816 to
"RDAC V2.out" .intvecs ==> .intvecs
satisfy the specified memory width of 4
"RDAC V2.out" .text ==> .text
"RDAC V2.out" .const ==> .const
"RDAC V2.out" .cinit ==> .cinit
'Finished building: RDAC V2.hex'
' '

  • 0
    Guru 86755 points
    Hi Vic,

    Are you using Tiva Launchpad? You need this string below at Post Build Steps. Alternatively you can just append your code to a Tiva Launchpad example program like "hello", which generates a .bin file.

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

    - kel
  • 0 in reply to Markel Robregado
    Prodigy 80 points

    No that line doesn't work.

    I'm not using Launchpad,  I am using the TM4C1231H6PZI Tiva.  I do have a launchpad and I will try building with that and see what happens.

  • 0
    TI__Guru**** 173310 points

    Vic Elias2 said:
    'Generate BIN'
    "C:/ti/ccsv6/utils/tiobj2bin/tiobj2bin" "RDAC V2.out" "RDAC V2.bin" "C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.2/bin/armofd" "C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.2/bin/armhex" "C:/ti/ccsv6/utils/tiobj2bin/mkhex4bin"
    ' '

    Vic,

    The binary file is likely being generated but named as "RDAC" without the .bin extension. Can you check if that is the case?
    This is because of a known limitation where the hex tool is not able to handle spaces in file names (see this forum thread). In this case, the binary file itself should be valid, so you can either rename it, or you change the post-build command such that the name of the output binary file does not contain spaces.

  • 0 in reply to AartiG
    Prodigy 80 points
    I think you found the problem.
    I found a 49K file simply named RDAC in that directory, no RDAC V2.bin so I am assuming the RDAC file is the .bin file.
    I wasn't able to find that forum thread on my own.
    Thanks for the help.