I am working with C54CST Board. I use Code Composer Studio 3.1 to make .out file from file .pjt (some available examples of board). And then I use some utilities of CSTHost to make file .hex from file .out. But when I load file .hex onto board, it does not work. If I use some available .out files of examples, it works properly. I think this may be the error of the .out file.
Please tell me how to correct this error.
Nguyen Dang Tu
> I am working with C54CST Board. I use Code Composer Studio 3.1 to make .out
> file from file .pjt (some available examples of board). And then I use some
> utilities of CSTHost to make file .hex from file .out. But when I load file
> .hex onto board, it does not work. If I use some available .out files of
> examples, it works properly. I think this may be the error of the .out file.
Suggest to verify with Spirit DSP that their CSTHost utility works with CCS v3.1.
v3.1 has changes from v2.2 related to format of .out file; possibly Spirit's utility
does not handle these (yet).
One thing you might try is to set compiler option:
and rebuild All. This will force .out file debug/symbol format to COFF. But even so
Spirit may need to update your utility.
If you search the CCS v3.1 Help file you can find the info below (which is not
present in the Build Options dialog!). DWARF format is also known as ELF format.
Note TI's comment about "older debuggers or customer tools" :-)
-g or --symdebug:dwarf Generates DWARF symbolic debugging directives
used by the debugger and enables assembly
source debugging in the assembler. Use this
option to generate debug information when your
application contains C++ files. For information
on the DWARF debug format, see the "DWARF
Debugging Information Format Specification",
1992-1993, UNIX International, Inc.
--profile:breakpt Disables optimizations that would cause incorrect
behavior when using a breakpoint-based profiler.
--profile:power Enables power profiling which produces instrument
code for the power profiler.
--symdebug:coff Enables symbolic debugging using the alternate
STABS debugging format. This may be necessary to
allow debugging with older debuggers or custom
tools, which do not read the DWARF format.
--symdebug:none Disbles all symbolic debugging output. This option
is not recommended; it prevents debugging and most
performance analysis capabilities.
--symdebug:skeletal Generates as much symbolic debugging information
as possible without hindering optimization.
Generally, this consists of global-scope
information only. This option reflects the
default behavior of the compiler.