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.

TMS470 Codgen Tool Options for creating an absolute listing of input modules

Other Parts Discussed in Thread: LM3S1911

I'm using CCSv4.2.4.00033 to build a C project for Stellaris LM3S1911 (ARM CortexM3).  I'm debugging a problem and I would like to have an absolute listing of the input C files, showing the absolute addresses.  What is the easiest way to do this?  I see the linker option --run_abs which I was hoping would just create these listing files, but this option alone is not producing anything for me.  Does this work with he absolute lister described in the assembly language tools users guide? If so how?

By the way, I'm not 100% sure what codegen version I'm using.  The CCS build options say "Code Generation tools: TI v4.6.4" and "Effective Code Generation tools: TI v4.9.0".

-Ruben

  • Ruben,

    Creating absolute listing files requires multiple steps that are outside the norm of the usual compile and link sequence.  So, this process is not well integrated into CCS builds.  You can do it with the post-build steps.  Please see this thread.

    Thanks and regards,

    -George

  • George,

    Thanks for the answer.  I will try to get it going.  What is the difference or relation between linker options "--run_abs" and "--absolute_listing"? The absolute lister description only deals with using "--absolute_listing" in the final step of invoking the linker.  What then is "--run_abs" useful for?

    Ruben

    Georgem said:

    Creating absolute listing files requires multiple steps that are outside the norm of the usual compile and link sequence.  So, this process is not well integrated into CCS builds.  You can do it with the post-build steps.  Please see this thread.

  • I have some more follow-on questions to this.  I have added the post build steps to my project to run abs470 and then cl470 –absolute_listing.  After CCS runs abs470 I get a bunch of .abs files which is good.  I have a question and a problem with this: 

    1. QUESTION: Why don’t I get .abs files for some of my input files? I have abs files for many rts library modules like _printfi.abs, boot.abs, etc., however I don’t see a “main.abs” file corresponding to my “main.c” file in the project.  Instead, I see a bunch of .abs files with autogenerated names like “0034810.abs”.  I have to search through these files to determine which one corresponds to my input files.
    2. PROBLEM: The assembler is choking on the “–-absolute_listing” step with an error about an include file from a .copy statement not being found. See below.

    -----Excerpt of build output-----

    Instruments/ccsv4/tools/compiler/tms470/bin/cl470.exe" "-aa" "C:/Documents and Settings/a0322160/My Documents/CCS Workspaces/MyProject/Debug_LM3S1911/0470410.abs"

    "C:/Documents and Settings/a0322160/My Documents/CCS Workspaces/MyProject/Debug_LM3S1911/0470410.abs", ERROR!   at line 391:

     [E1000]

             Include/Copy file not found or opened

                    .copy       "0470410"

    -----End Excerpt of build output -----

     

    Am I doing something wrong with this? I suspect that both 1 & 2 have to do with the fact that the project is built with (--symdebug:dwarf) because I see a note about this in the absolute lister description and it suggests using the –e options when running abs470.  I don’t think it’s practical for me to use the –e options to list all the .C files and .h files form my project in the command line so I wonder if I can even get off the ground with this.

     

    Backing up a minute, what I'm after is a way to match an address to the corresponding line of source code.  It seems like a common problem that we would have a canned solution for.  Am I over engineering this?

     

    Ruben