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

CCSv4.1 Issue with mkhex2bin.exe (Stellaris - LM3S8962)

Robb S
Expert 3120 points
Other Parts Discussed in Thread: EK-LM3S3748

During project rebuild active project, after compile completes and hello.out file is generated, the mkhex2bin.exe attempts to run. 

"C:/StellarisWare/boards/ek-lm3s3748/hello/hello_ccs.cmd"

<Linking>

'Finished building target: hello.out'

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

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

 

"C:/Program Files/Texas Instruments/ccsv4/utils/tiobj2bin/tiobj2bin.bat" "hello.out" "hello.bin" "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/tms470/bin/ofd470.exe" "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/tms470/bin/hex470.exe" "C:/Program Files/Texas Instruments/ccsv4/utils/tiobj2bin/mkhex4bin.exe"

error: -image requires ROMS directive

Is there an explanation for this error message, and is there a way to resolve the issue.

CCS will download the .out file into the target for debugging, but the .bin file is never generated.

Any help is greatly appreciated.

Best Regards,

Robb

  • TI__Guru**** 472411 points

    Hi Robb,

    Did you simply import the existing CCSv4 project into your workspace and hit "build"? Or did you tweak your project a bit? I generated the hello.bin with just the import and build right out of the box.

    ki