• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 2268 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.

Hex2000 and post build steps

Rob Clarke
Prodigy 80 points
Other Parts Discussed in Thread: CCSTUDIO

Hi

I am using CCS V4.2.3.00004.

I am building my project and trying to automatically translate my .out file to an .hex file for use with my programming software

I amusing the post build step "

${CG_TOOL_ROOT}/bin/hex${CG_TOOL_SUFFIX}.exe" -i "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.hex" -order MS -romwidth 16

In the console, a build completes with no errors reported and it all looks like the .hex file has been produced but upon inspecting the build directory I only find .out file and no hex file?? What am I doing wrong???

  • 0
    TI__Guru**** 173310 points

    Rob,

    The command itself looks fine and works for me. The only thing missing in what you've shown here is a " in the beginning of the command, but I assume that was just a typo.

    Does the CCS build console show the hex conversion happening? Should look something like:

    C:/CCStudio_v4.2.3.00004/ccsv4/utils/gmake/gmake --no-print-directory post-build

    "C:/CCStudio_v4.2.3.00004/ccsv4/tools/compiler/C2000 Code Generation Tools 6.0.1/bin/hex2000.exe" -i "test_f28335.out" -o "test_f28335.hex" -order MS -romwidth 16

    Translating to Intel format...

    "test_f28335.out" ==> .cinit
    "test_f28335.out" ==> .text
    "test_f28335.out" ==> .econst
    ' '

     

  • 0 in reply to AartiG
    Prodigy 80 points

    Hi

    The console shows it running

    This is what I see below:

     

     

    C:/Program Files/Texas Instruments/ccsv4/utils/gmake/gmake --no-print-directory post-build

    'Create flash image: Intel-HEX'

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c2000/bin/hex2000.exe" -i "H:/Software/dsp software EXP02/recieverflashEXP02.out" -o "H:/Software/dsp software EXP02/recieverflashEXP02.hex" -order MS -romwidth 16

    Translating to Intel format...

    "H:/Software/dsp software EXP02/recieverflashEXP02.out" ==> non_volatile

    "H:/Software/dsp software EXP02/recieverflashEXP02.out" ==> Flash28_API

    "H:/Software/dsp software EXP02/recieverflashEXP02.out" ==> .econst

    "H:/Software/dsp software EXP02/recieverflashEXP02.out" ==> .cinit

    "H:/Software/dsp software EXP02/recieverflashEXP02.out" ==> secureRamFuncs

    "H:/Software/dsp software EXP02/recieverflashEXP02.out" ==> .text

    "H:/Software/dsp software EXP02/recieverflashEXP02.out" ==> csm_rsvd

    "H:/Software/dsp software EXP02/recieverflashEXP02.out" ==> codestart

    "H:/Software/dsp software EXP02/recieverflashEXP02.out" ==> passwords

    ' '

    Build complete for project receiverFlashEXP02

    When I browse to H:/Software/dsp software EXP02/ I see no .hex file only .out file?

     

  • 0 in reply to Rob Clarke
    TI__Guru**** 173310 points

    This is definitely odd and I cannot reproduce it. 

    Does it work when you run the command directly from a command prompt rather than from CCS?
    What if you change the location of the .out and .hex file to a directory within C:\? Does that make a difference?

  • 0 in reply to AartiG
    Prodigy 80 points

    Hi

    Yes if I change the loaction of the output files to a C:\ directory it does work so I guess CCS is not happy with the path.

    I have experienced this before with other design tools but thought now in 2011 these sort of issues were non-existant!

     

    thanks for your help