Filter
Top Products
2 IMPLEMENTING THE DEBUG MONITOR
EPSON S1C33 FAMILY DEBUG MONITOR
OPERATION MANUAL
6
2.3 Building an Application Program
The S5U1C330M2S modules are provided as a library file "mon33*.lib" in the directory "lib\". Link this library to
the user modules.
When using the serial interface on the S1C33 chip and the S5U1C330MxD1 board, link "mon33ch0.lib" (Ch.0 is
used) or "mon33ch1.lib" (Ch.1 is used) accordingly. When not using the serial interface on the S1C33 chip and the
S5U1C330MxD1 board, create serial I/O routines separately and link "mon33.lib".
Specify the "lib\" directory of the S5U1C330M2S as a library path in the linker command file when linking.
Example: "dmt33004\dmt33004.cm"
;Map set
-code 0x0c00000 ; set relative code section start address
-bss 0x06ff640 ; set relative bss section start address
;Library path
-l c:\CC33\lib .... CC33 standard library path
-l ..\lib .... S5U1C330M2S library path (c:\E0C33\mon33\lib)
;Executable file
-o dmt33004.srf
;Object files
m3s_boot.o
;Library files
string.lib
ctype.lib
idiv.lib
mon33ch1.lib .... S5U1C330M2S library to be linked
Since all the source codes of the debug monitor are provided in the directory "src\", it is possible to customize the
debug monitor if necessary. In this case, rebuild the library using "mon33*.mak" (make file for creating
"mon33*.lib") in the directory "lib\".
S5U1C330M2S allows the debugger db33 to write the target program to be debugged in the RAM or Flash memory
on the target board. In this case, it is not necessary to create a target object linked to the debug monitor. When the
S5U1C33xxxDx board (S5U1C33104D1, S5U1C33209D1, etc.) is used, the target program can be downloaded to
the RAM or Flash memory and can be debugged by writing S5U1C330M2S and a simple boot program to the ROM.
When executing the target program in the external ROM on the target board, link the debug monitor to the target
program and create an object that is mapped to the external ROM.