Motorola HC12 - Manual (Page 74)

User’s Manual MCUez HC12 Assembler
74 Files MOTOROLA
Files
4.4.4 Listing Files
After a successful assembly session, the macro assembler generates a listing file
containing each assembly instruction with its associated hexadecimal code.
This file is generated when the option
-L is activated, even if the macro
assembler generates an absolute file. This file is written to the directory given
in the environment variable TEXTPATH. If that variable contains more than one
path, the listing file is written in the first directory specified. If this variable is
not set, the listing file is written in the directory where the source file was found.
Listing files always get the extension .lst.
Section 10. Assembler Listing File
describes the format of this file.
4.4.5 Debug Listing Files
After a successful assembling session, the macro assembler generates a debug
listing file, which will be used to debug the application. This file is always
generated, even when the macro assembler generates an absolute file. The
debug listing file is a duplicate of the source, where all the macros are expanded
and the include files merged. This file (with the extension .dbg) is written to the
directory listed in the environment variable OBJPATH. If that variable contains
more than one path, the debug listing file is written to the first directory given.
If this variable is not set, the file is written in the directory where the source file
was found. Debug listing files always get the extension .dbg.
4.4.6 Error Listing Files
If the macro assembler detects any errors, it creates an error file. The name and
location of this file depend on the settings from the environment variable
ERRORFILE.
If the macro assembler’s window is open, it displays the full path of all include
files read. After successful assembly, the number of code bytes generated and
the number of global objects written to the object file are displayed.
Figure 4-1
shows the different structures associated with the assembler.