Zilog EZ80F916 - Manual (Page 101)

UM014423-0607 Using the Integrated Development Environment
ZiLOG Developer Studio II
eZ80Acclaim! ® User Manual
81
COPY DATA ROM
COPY CODE ROM
causes both the
CODE
and
DATA
segments to be copied to ROM. These segments are
then copied by the startup code to the appropriate RAM addresses, completing the
actions associated with the Copy to RAM configuration.
NOTE: To use the Copy to RAM configuration (unless you have your own complex and
carefully designed allocation of code segments into particular modules), the
Distinct Code Segment for Each Module check box in the Advanced page (see
“Distinct Code Segment for Each Module” on page 68) must be deselected.
Selecting that check box prevents the linker from being able to group the CODE
segments from all your code modules into a single contiguous block that can be
copied to RAM automatically by the linker commands that are used in this
configuration.
•
Custom
Choose this option if the other three options do not provide the right configuration. As
a result, you are required to define all of the segment-to-space mappings, depending
on the hardware configuration of the application board. You also need to include your
own startup module for this selection.
•
Deprecated CUSTOM Configuration
This configuration was provided in earlier releases of ZDS II for eZ80Acclaim! before
the 4.10.0 release. It is supported for backward compatibility. In those earlier releases,
this configuration was called “Custom,” but, in fact, it was nearly identical to the
Standard configuration. The only difference was that the ordering of segments was left
to the user and that the STRSECT segment was left in RAM instead of ROM. That
segment contains string literals and should always be placed in ROM for production
code but can be kept in RAM at times for debugging.
In the 4.10.0 and subsequent releases of ZDS II, the Custom link configuration is used
to support truly customized link command files. ZiLOG recommends that if you have
an older project that used the Deprecated Custom configuration, you convert it either
to the Standard configuration (by changing to that setting and verifying that the minor
changes in link commands cause you no problems) or to the Custom configuration (by
saving your existing link command file and selecting the Use Existing button (see
“Use Existing” on page 83). At some future time, the Deprecated Custom
configuration might no longer be supported in ZDS II.
Always Generate from Settings
When this button is selected, the linker command file is generated afresh each time you
build your project; the linker command file uses the project settings that are in effect at the
time. This button is selected by default, which is the preferred setting for most users.
Selecting this button means that all changes you make in your project, such as adding