SDKZSPF LSI, SDKZSPF Datasheet - Page 96

• Manufacturer Part Number: SDKZSPF
• Manufacturer: LSI

Specifications of SDKZSPF

• Lead Free Status / Rohs Status: Supplier Unconfirmed

5.2 Sections
5.3 Symbols
5-2
By default, the linker generates .text, .data and .bss sections. The
.text sections contains code, .data contains data, and .bss contains
uninitialized data. If there are additional user-defined sections specified
in the linker script file, the linker generates them also.
By default, .bss follows .data in data memory unless relocated using a
linker script command.
The following section names have special meaning only on the ZSP400
linker:
Code or data in these sections is placed in the appropriate external
instruction or data memory, with the particular external page selected by
the number in the section name.
On the ZSP400 architecture, the offset of a call immediate instruction
must be even. If the assembler cannot resolve this offset, the linker will.
If the offset is odd, the linker displays an error message. Because the
assembler automatically aligns call immediate instructions on an even
address, this error occurs only if the call target was on an odd address.
To resolve this error, align the call target on an even address, using the
.walign 2 directive.
By default, program execution begins at __start. The entry point can be
altered by specifying an alternate address, using the -e option. For
example, the following command causes execution to begin at address
0xABCD:
The C stack and heap always lie in internal data memory.
Linker
Copyright © 1999-2003 by LSI Logic Corporation. All rights reserved.
.exttext_0 through .exttext_15
.extdata_0 through .extdata_15
sdld -e 0xabcd