I'm just passing this along from experience after troubleshooting this issue (only a true engineer may laugh at the end).
I had been using Code Composer Studio 3.3 with our project, but then corporate mandated a switch to Windows 7, so I had to upgrade to Code Composer Studio v5.1. I followed the instructions for importing the project, but of course it didn't build (with CCS 3.3 it built fine).
The first fix was specifying "far" for the memory model in the project properties - got that tip from a posting in the CCS forum.
The next involved post build. In CCS 3.3, I had the following command in the properties (General - Build Command): hex6x .\Debug\myproject.out Hex6x.cmd. Ok, the name of the out file really isn't "myproject.out", but I'll call it that to protect the its true identity; the name of the file isn't important. This worked fine on my WindowsXP machine running CCS 3.3. It correctly generated the hex file.
But on Window7 running CCS v5.1, things didn't go well. First, it's funny that when CCS v5.1 imported this project, it created a bat file, post_BuildStep_Debug.bat (and this is the file specified for post build - project properties - CCS Build - "Steps" tab - Post-build steps - Command: "${PROJECT_ROOT}/postBuildStep_Debug.bat". But no matter, this batch file eventually calls "hex6x .\Debug\myproject.out Hex6x.cmd".
Things went "haywire" in CCS's Console window. It kept repeating:
'/***********************************************************************************' is not recognized as an internal or external command,
operable program or batch file.
'This' is not recognized as an internal or external command,
operable program or batch file.
'options' is not recognized as an internal or external command,
operable program or batch file.
'Invoke' is not recognized as an internal or external command,
operable program or batch file.
Over and over it kept repeating. It was at the end of the day, so I let it run. It was still repeating the next morning. I, of course, started checking the TI forums but nothing. A good half a day was spent debugging this.
OK, let's cut to the chase. Look at the command line: "hex6x .\Debug\myproject.out Hex6x.cmd" Well, .cmd files are technically Windows/DOS executable files. So my Windows PC saw "hex6x" and rather than using the hex6x.exe file in C:\ti\ccsv5\tools\compiler\C6000\bin, instead it was trying to execute Hex6x.cmd. Hmm..., it worked fine on WindowsXP + CCS3.3, but not Windows7 + CCSv5.1,...go figure. After I change the parameter file to "generate_hex.cmd" it worked fine on the latter also.
The moral of this story is, don't name your hex6x parameter file Hex6x.cmd. Actually, its best not to name any file with the .exe, .com, or .cmd extension.
****
No follow-up is being requested, I'm just passing along my experience. I felt this item fit better in the Compiler forum (rather than the CCS forumn) since hex6x is part of the compiler tools.
