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

• Manufacturer Part Number: s5u1c33000c
• Description: Cmos 32-bit Single Chip Microcomputer S5u1c33000c Manual
• Manufacturer: Epson Electronics America, Inc.

-bssblock command
Format:
Sample description: -bssblock MAIN_RAM1 {main.o test.o}
Explanation:
Default:
Note:
-ucodeblock command
Format:
Sample description: -ucodeblock CACHE_OBJ {speed.o cache.o}
Explanation:
S5U1C33000C MANUAL
(C COMPILER PACKAGE FOR S1C33 FAMILY) (Ver. 4)
-bssblock <Block name> {<File name ... <File name>}
Unless specified by this command, all BSS sections in the object files are located in a block
named DEFAULT_BSS.
-ucodeblock <Block name> {<File name ... <File name>}
This command combines the BSS sections included in the relocatable object files
specified in { } to create a new block.
The BSS sections are located at successive locations in this block in the specified order.
At least one space or tab is required between -bssblock and <block name>.
When specifying multiple files, be sure to enter at least one space, tab, or line feed
between <file name> entries.
File names in { } can be written in two or more separate lines.
Example) -bssblock RAM1
Up to 256 blocks can be defined.
A block name can contain up to 130 characters and are case-sensitive.
An object file name can contain up to 256 characters, including the path.
Up to 4,000 files can be specified in { }.
Defining two or more blocks with the same block name results in a warning.
In this case, the first block defined is effective.
Example) -bssblock RAM1 {test1.o test2.o}
Block names cannot be preceded by the symbol '@' or '#'.
No object file names that are the same can be specified in { } (except when they have
different paths).
At least one object file must be specified in { }.
If any file name specified in { } does not match the link file (including the path), a
warning is given and the file is processed as being not specified. If this results in no
valid files being specified in { }, an error results. However, this does not apply when
library objects are specified (i.e., "xxx.lib:xxx.o" is specified).
No errors occur even when the block name definition is not referenced by the -addr
command. However, the BSS sections in the specified object files remain located in the
DEFAULT_BSS block until addresses are specified by -addr
No default block names (DEFAULT_CODE, DEFAULT_DATA, or DEFAULT_BSS)
can be used for the block name defined here. However, these default block names can be
used unless they consist entirely of uppercase letters. (Example: Default_Bss can be
used.)
This command maps the CODE sections included in the specified object files into the
same area (shared block). This is effective in cases where one RAM area is shared by
multiple object codes specified and the object codes are executed by transferring to the
RAM through a time-multiplexed channel. The location where the object codes are
actually located may be specified by -codeblock. (By default, they are located in the
DEFAULT_CODE block.)
The block is assigned the largest size among those of the sections to be mapped.
At least one space or tab is required between -ucodeblock and <block name>.
When specifying multiple files, be sure to enter at least one space, tab, or line feed
between <file name> entries.
{
}
-bssblock RAM1 {test3.o test4.o}
boot.o
main.o
sub.o
EPSON
(Link processing in lk33 Ver. 3.0)
... Effective
... Has no effect
CHAPTER 12: LINKER
211