The TMS320C28x absolute lister is a debugging tool that accepts linked object files as input and creates .abs files as output. These .abs files can be assembled to produce a listing that shows the absolute addresses of object code. Manually, this could be a tedious process requiring many operations; however, the absolute lister utility performs these operations automatically.

9.1 Producing an Absolute Listing

Figure 9-1 illustrates the steps required to produce an absolute listing.

9.2 Invoking the Absolute Lister

The syntax for invoking the absolute lister is:

The absolute lister produces an output file for each file that was linked. These files are named with the input filenames and an extension of .abs. Header files, however, do not generate a corresponding .abs file.

Assemble these files with the --absolute_listing assembler option as follows to create the absolute listing:

cl2000 --absolute_listing filename .abs

The -e options affect both the interpretation of filenames on the command line and the names of the output files. They should always precede any filename on the command line.

The -e options are useful when the linked object file was created from C files compiled with the debugging option (--symdebug:dwarf compiler option). When the debugging option is set, the resulting linked object file contains the name of the source files used to build it. In this case, the absolute lister does not generate a corresponding .abs file for the C header files. Also, the .abs file corresponding to a C source file uses the assembly file generated from the C source file rather than the C source file itself.

For example, suppose the C source file hello.csr is compiled with the debugging option set; the debugging option generates the assembly file hello.s. The hello.csr file includes hello.hsr. Assuming the executable file created is called hello.out, the following command generates the proper .abs file:

abs2000 -ea s -ec csr -eh hsr hello.out

An .abs file is not created for hello.hsr (the header file), and hello.abs includes the assembly file hello.s, not the C source file hello.csr.

9.3 Absolute Lister Example

This example uses three source files. The files module1.asm and module2.asm both include the file globals.def.

module1.asm

.text array .usect ".ebss",100 dflag .usect ".ebss", 2 .copy globals.def MOV ACC, #offset MOV ACC, #dflag

module2.asm

offset .usect ".ebss", 2 .copy globals.def MOV ACC, #offset MOV ACC, #array

globals.def

.global dflag .global array .global offset

The following steps create absolute listings for the files module1.asm and module2.asm:

--output_file=bttest.out --map_file=bttest.map module1.obj module2.obj MEMORY { PAGE 0: ROM: origin=2000h length=2000h PAGE 1: RAM: origin=8000h length=8000h } SECTIONS { .data: >RAM .text: >ROM .ebss: >RAM } .nolist array .setsym 000008000h dflag .setsym 000008064h offset .setsym 000008066h .data .setsym 000008000h edata .setsym 000008000h .text .setsym 000002000h etext .setsym 000002008h .usect .setsym 000008000h end .setsym 000008068h .setsect ".text",000002000h .setsect ".data",000008000h .setsect ".ebss",00008000h .list .text .copy "module1.asm" .nolist array .setsym 000008000h dflag .setsym 000008064h offset .setsym 000008066h .data .setsym 000008000h edata .setsym 000008000h .text .setsym 000002000h etext .setsym 000002008h .usect .setsym 000008000h end .setsym 000008068h .setsect ".text",000002004h .setsect ".data",000008000h .setsect ".ebss",00008066h .list .text .copy "module2.asm"