Motorola dsp assembler Reference Manual

Assembler Listing File Format
Memory Utilization Report Format
D-4
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA_DSP_ASSEMBLER_REFERENCE_MANUAL_D-15'>MOTOROLA_DSP_ASSEMBLER_REFERENCE_MANUAL_D-13'>MOTOROLA_DSP_ASSEMBLER_REFERENCE_MANUAL_D-11'>MOTOROLA_DSP_ASSEMBLER_REFERENCE_MANUAL_D-9'>MOTOROLA_DSP_ASSEMBLER_REFERENCE_MANUAL_D-7'>MOTOROLA_DSP_ASSEMBLER_REFERENCE_MANUAL_D-5'>MOTOROLA
block in the X memory report is of type CODE because it is overlay code to be executed
in P memory.
The label from the source file is included on the report under the label column, since there
was a label associated with the DS directive.  If there had been no label, the label column
on the report would have been blank.  The section and overlay address columns are emp-
ty because there is no current section and no overlay in progress at this point in the
source.
In the next-to-last line of the X memory report (start address $400), there is an entry of
type CODE with an overlay address. This is the corresponding load entry for the first line
in the P memory report, and indicates that this is an overlay block. Separate report records
are generated as a result of the ORG directive in the source which has the form ORG
P:,X:$400, signifying an overlay. In the X memory report, the overlay address is P:0 and
the R in parentheses means that the overlay address is the runtime address. Conversely,
the first line in the P memory report shows an overlay address of X:400; the L in paren-
theses means that the overlay address is the load time address.

---

Assembler Listing File Format
Assembler Listing Format
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
D-5

---

Assembler Listing File Format
Assembler Listing Format
D-6
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA

---

Assembler Listing File Format
Assembler Listing Format
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
D-7

---

Assembler Listing File Format
Assembler Listing Format
D-8
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA

---

Assembler Listing File Format
Assembler Listing Format
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
D-9

---

Assembler Listing File Format
Assembler Listing Format
D-10
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA

---

Assembler Listing File Format
Assembler Listing Format
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
D-11

---

Assembler Listing File Format
Assembler Listing Format
D-12
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA

---

Assembler Listing File Format
Assembler Listing Format
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
D-13

---

Assembler Listing File Format
Assembler Listing Format
D-14
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA

---

Assembler Listing File Format
Assembler Listing Format
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
D-15

---

Assembler Listing File Format
Assembler Listing Format
D-16
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA

---

Assembler Listing File Format
Assembler Listing Format
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
D-17

---

Assembler Listing File Format
Assembler Listing Format
D-18
DSP ASSEMBLER REFERENCE MANUAL
MOTOROLA

---

MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
E-1
Appendix E
MOTOROLA DSP OBJECT FILE FORMAT (COFF)
E.1
  INTRODUCTION
The Motorola DSP Assembler and Linker produce a binary object file in a modified form
of the AT&T Common Object File Format (COFF). COFF is a formal definition for the
structure of machine code files. It originated with Unix System V but has sufficient flexibil-
ity and generality to be useful in non-hosted environments. In particular, COFF supports
user-defined sections and contains extensive information for symbolic software testing
and debugging.
Later sections describe the COFF implementation for the Motorola family of digital signal
processors. The DSP COFF format has been altered to support multiple memory spaces
and normalized to promote transportability of object files among host processors. See
section E.4 for a list of differences between the Motorola DSP object file format and stan-
dard COFF. For a more general discussion of COFF the following reference may be use-
ful:
Gintaras R. Gircys, Understanding and Using COFF, O’Reilly & Associates,
1988 (ISBN 0-937175-31-5).
E.2
  OBJECT FILE STRUCTURE
A DSP COFF object file consists of up to eight groups of object file information.  Some of
these groups are optional, depending on the type of object file generated, and others may
have repeating occurrences.  The basic object file components are:
•
File header
•
Optional header
•
Section headers
•
Section data
•
Relocation information
•
Line numbers
•
Symbol table
•
String table

---