The MSP430 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:

cl430 --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:

abs430 -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

.global dflag .global array .global offset .bss dflag,1 .bss array,100 .text MOV &array,R11 MOV &offset,R12 ADD R12,R11 MOV @R11,&dflag

module2.asm

.global dflag .global array .global offset .bss offset,1 .text MOV &offset,R14

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 { RAM: origin=0x0200, length=0x0800 FLASH: origin=0x1100, length=0xEEE0 } SECTIONS { .bss: >RAM .text: >FLASH } .nolist .text .setsym 000001100h __text__ .setsym 000001100h etext .setsym 000001112h __etext__ .setsym 000001112h .bss .setsym 000000200h __bss__ .setsym 000000200h end .setsym 000000266h __end__ .setsym 000000266h array .setsym 000000201h dflag .setsym 000000200h offset .setsym 000000265h .setsect ".text",000001100h .setsect ".bss",000000200h .setsect ".debug_line",000000000h .list .text .copy "module1.asm" .nolist .text .setsym 000001100h __text__ .setsym 000001100h etext .setsym 000001112h __etext__ .setsym 000001112h .bss .setsym 000000200h __bss__ .setsym 000000200h end .setsym 000000266h __end__ .setsym 000000266h array .setsym 000000201h dflag .setsym 000000200h offset .setsym 000000265h .setsect ".text",00000110eh .setsect ".bss",000000265h .setsect ".debug_line",00000003ah .setsect ".debug_info",00000014fh .list .text .copy "module2.asm"