s5u1c33000c Epson Electronics America, Inc., s5u1c33000c Datasheet - Page 237

no-image

s5u1c33000c

Manufacturer Part Number
s5u1c33000c
Description
Cmos 32-bit Single Chip Microcomputer S5u1c33000c Manual
Manufacturer
Epson Electronics America, Inc.
Datasheet
Example for locating virtual and shared blocks
Notes: • Source-level debugging is possible for the libraries with debug information in the default code
S5U1C33000C MANUAL
(C COMPILER PACKAGE FOR S1C33 FAMILY) (Ver. 4)
The following presents examples of how to locate object files using virtual and shared blocks.
Example: Command file
The actual block mapping for the above example is shown in Figure 12.6.4.1.
• The absolute files in virtual blocks do not have their source debug information mapped into
block (DEFAULT_CODE).
For virtual blocks (@#DEFAULT_CODE), however, because debug information is not
mapped into virtual areas, source-level debugging in a virtual area cannot be performed.
virtual memory.
-v3
-defaddr IN_RAM=0x0
-defaddr EXT_RAM=0x600000
-defaddr EXT_ROM=0xc00000
-codeblock OBJ1
{
}
-ucodeblock OBJ2
{
}
-addr IN_RAM
{
}
-addr EXT_ROM
{
}
sample1.o
sample2.o
sample3.o
sample4.o
sample5.o
sample.lib
sample2.o
sample3.o
sample1.o
sample4.o
DEFAULT_BSS
@DEFAULT_DATA
@#OBJ1
@OBJ2
DEFAULT_CODE
OBJ1
DEFAULT_DATA
... Use lk33 Ver. 3.0 or later commands
... Define address symbols
... Define blocks
... Define shared blocks
... Locate blocks beginning here
... Locate "OBJ1" as a virtual block
... Locate the shared block "OBJ2" as a virtual block
... Specify objects and a library
same area (at the same address)
The CODE sections in sample1.o and sample4.o are set in the
(Objects cannot be located directly)
EPSON
(Link processing in lk33 Ver. 3.0)
CHAPTER 12: LINKER
221

Related parts for s5u1c33000c