User`s guide

System LSI Division, Semiconductor Business
This option is useful to build a library file. As mentioned earlier a NOP is inserted in all code sections
(CODE and ECODE), so that during linking time any of the CODE section can be placed in EEPROM area.
>CalmAsm16 –d –L input.s
3.1.3 Linker
3.1.3.1 EEPORM library (from V1.54f5S)
Following linker option is supported:
-9 <elib> Where elib is a library file. Modules from this file will be placed in EEPROM area if requested from
EEPROM code.
Linker supports two kinds of library files,
–l <lib> Option to link with normal library files.
–9 <elib> Option to link with EEPROM libraries. Where the library has been built using -b or –d assembler
option.
A library module requested form CODE section (ROM area) is searched in library files mentioned in –l <lib> option.
If the requested module is not found then it is searched in library files mentioned in –9 <elib> option. The
requested module is then kept in ROM area.
A library module requested form ECODE section (EEPROM area) is searched in library files mentioned in –9 <elib>
option. If the requested module is not found then it is searched in library files mentioned in –l <lib> option. The
requested module is then kept in EEPRROM area.
If same library module is requested from CODE and ECODE section then it is searched in library files mentioned in –l
<lib> option and then in –9 <elib> option. The requested module is then kept in ROM area.
>CalmLink16 –l calm16_1.lib –l calm16_2.lib –9 eep_lib1.lib –9 eep_lib2.lib <other options> <input object files>
3.1.3.2 Memory Description file (MD file from V1.56aS)
The linker combines input sections from one or more object and library files to create executable image (HEX
and HXD files). The generated output file can be viewed as group of regions with every region having different
(or same) load and run address.
MD file mechanism enables user to specify memory map of an image to the linker. It gives complete control
over grouping and placement of regions. MD file can be used for complex memory maps, where code and data
must be placed into different areas of memory. It can be used when device has different types of memories.
Image regions are placed in the system memory map at load time. Before you can execute the image, you
might have to move some of its regions to their execution addresses. For example, initialized RW data (IDATA)
might have to be copied from its load address in ROM (ILOAD) to its execution address in RAM.
MD file can be provided to linker with –md <file> or –7 <file> options.
Invocation:
Property of Samsung Electronics Co., Ltd. 3