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

how to create hexutil.cmd in ccsv4

sandeepb
Prodigy 110 points

Other Parts Discussed in Thread: TMS320C28346

hi,

i am using ccsv4 for tms320c28346 microcontroller. i want to invoke hexconverter utility through a command file.

my question is- How to create a hexutil.cmd file in my project? how do i link this file to my project?

  • 0
    TI__Guru**** 173310 points

    The command file that will be passed to the hex converter does not need to be added/linked to the project in CCS. You can create the file within CCS if you wish just as you would any other source or linker command file and save it, but exclude it from build (right-click on file name and Exclude File from build). The hex converter is typically invoked as a post-build step in CCS, and there you can pass this hexutil.cmd file to the hex2000.

    Please refer to the C28x Assembly Language Tools Users Guide for details on invoking the hex converter from a command line and use that command as the post-build step in CCS.

  • 0 in reply to AartiG
    Prodigy 110 points

    thanks for your reply,

    i invoke hex2000 in CCS by command line in post build steps to convert .out to .a00 format. it works perfectly fine !

    Now! i create a hexutil.cmd in CCS project (excluded from build) and pass this file to hex2000 at post build step as follows:-

    Post-build step

    Command:

    C:\Program Files\Texas Instruments\ccsv4\tools\compiler\c2000\bin\hex2000 hexutil.cmd

    but build completes with following error:-

    post-build

    C:\Program Files\Texas Instruments\ccsv4\tools\compiler\c2000\bin\hex2000 hexutil.cmd

    fatal error: cannot open input file "hexutil.cmd": No such file or directory

    gmake[1]: [post-build] Error 1 (ignored)

    ' '

    Build complete for project

    i've referred spru513 there it is mentioned that to invoke hex utility by command file, enter:  hex2000 hexutil.cmd

    I also tried to give path of hexutil.cmd (which is in the project workspace) but that also didn't work. so i am stuck up with how to use a command file with hex2000?

    pls guide

    regards

  • 0 in reply to sandeepb
    TI__Guru**** 173310 points

    If you give the full path to hexutil.cmd it should work.

    As an example, something like the following works for me(where C:\CCSv41\c2000_workspace\f2812_array is my project folder):
    C:\Program Files\Texas Instruments\ccsv4\tools\compiler\c2000\bin\hex2000 C:\CCSv41\c2000_workspace\f2812_array\hexutil.cmd

    What does your command look like, and what does your hexutil.cmd contain?

  • 0 in reply to AartiG
    Prodigy 110 points

    thank you for your help!

    my project is xyz1 and my command looks as:

    case I

    C:\Program Files\Texas Instruments\ccsv4\tools\compiler\c2000\bin\hex2000 C:\CCSv4\workspace\xyz1\hexutil.cmd 

    the above has worked fine. thanks once again!

    case II

    earlier my command looked:

    C:\Program Files\Texas Instruments\ccsv4\tools\compiler\c2000\bin\hex2000 C:\Documents and Settings\User\My Documents\workspace\xyz1\hexutil.cmd

    which generated error : couldn't find file "C:\Documents.out "

    so i switched my workspace to the above one  C:\CCSv4\workspace\xyz1\hexutil.cmd 

    my problem is solved but a bit confused why in caseII the path to workspace is not clear to the utility?!

    regards

  • 0 in reply to sandeepb
    TI__Guru**** 173310 points

    Try enclosing the paths in double-quotes:

    "C:\Program Files\Texas Instruments\ccsv4\tools\compiler\c2000\bin\hex2000" "C:\Documents and Settings\User\My Documents\workspace\xyz1\hexutil.cmd"

  • 0 in reply to AartiG
    Prodigy 110 points

    Yes! as you say enclosing the path in double-quotes works. thats good.

    thank you.

    regards