
4. Occupied Area for Monitor Program
Table 1 Occupied Area for Monitor Program
ROM / RAM Occupied Area for Monitor Program
8KB / 512B Vector FFE8h to FFEBh, FFECh to FFEFh,
FFF4h to FFF7h
12KB / 768B RAM 6FFh
Vector FFE8h to FFEBh, FFECh to FFEFh,
FFF4h to FFF7h
16KB / 1KB RAM 6FFh to 7FFh
Flash memory C000h to C7FFh
Vector FFE8h to FFEBh, FFECh to FFEFh,
FFF4h to FFF7h
5. Precautions on Using R8C UART Debugger
5.1. When changing the communication speed and restarting the R8C
UART debugger after the R8C UART debugger ends.
The target MCU holds the baud rate value after the R8C UART debugger ends. Therefore,
when changing the communication speed and restarting the R8C UART debugger, a
communication error occurs. (The R8C UART debugger can be started when using the
previous communication speed). When changing the communication speed, turn off the
target power and turn on the power again.
5.2. ID code of user program
Set the ID code of the user program to all FFh when using the R8C UART debugger.
Table 2 Storing Address of ID Code (R8C/10 Group)
Address ID No. Vector Table
0FFDFh – 0FFDCh ID1 Undefined Instruction
0FFE3h – 0FFE0h ID2 Overflow
0FFE7h – 0FFE4h BRK Instruction
0FFEBh – 0FFE8h ID3 Address Match
0FFEFh – 0FFECh ID4 Single Step
0FFF3h – 0FFF0h ID5 Watchdog Timer,
Oscillation Stop Detection,
Voltage Monitor 2
0FFF7h – 0FFF4h ID6 Address Break
0FFFBh – 0FFF8h ID7 Reserved
0FFFFh – 0FFFCh (NOTES 1) Reset
NOTES
1. Refer to the hardware manual for the value set in 0FFFFh.
5.3. Area in which user program can be downloaded
As shown in Figure 3, a part of RAM or Flash Memory is used for the monitor program when
using the R8C UART debugger. The R8C UART debugger does not download the user
program in the area which overlaps with a monitor program when a user program overlaps
with a monitor program. Note that the R8C UART debugger does not perform an error
output at this time.
18
Comentarios a estos manuales