RL78/G10 CHAPTER 21 ON-CHIP DEBUG FUNCTION
R01UH0384EJ0311 Rev. 3.11 560
Dec 22, 2016
21.3 Securing of User Resources
To perform communication between the RL78 microcontroller and E1 on-chip debugging emulator, as well as each
debug function, the securing of memory space must be done beforehand.
If Renesas Electronics assembler or compiler is used, the items can be set by using linker options.
(1) Securement of memory space
The shaded portions in Figure 21-3 are the areas reserved for placing the debug monitor program, so user
programs or data cannot be allocated in these spaces. When using the on-chip debug function, these spaces must
be secured so as not to be used by the user program. Moreover, this area must not be rewritten by the user
program.
Figure 21-3. Memory Spaces Where Debug Monitor Programs Are Allocated
00000H
00002H
000C3H
000C4H
000CEH
FFEDFH
FFEDCH
000D8H
Code flash memory
Use prohibited
Debug monitor area
(10 bytes)
Security ID area
(10 bytes)
4 bytes
Debug monitor area
(2 bytes)
Note 2
Code flash
area
On-chip debug option byte area
(1 byte)
Internal RAM
SFR area
Stack area for debugging
(10 bytes)
Note 4
Note 3
Mirror area
Internal RAM
area
: Area used for on-chip debugging
Note 1
Notes 1. Address differs depending on products as follows.
Products Address
R5F10Y14, R5F10Y44 003FFH
R5F10Y16, R5F10Y46 007FFH
R5F10Y17, R5F10Y47 00FFFH
2. In debugging, reset vector is rewritten to address allocated to a monitor program.
3. When real-time RAM monitor (RRM) function and dynamic memory modification (DMM) function are used,
four bytes from FFEDCH to FFEDFH are consumed. Otherwise, this area can be used as the internal RAM.
4. Since this area is allocated immediately before the stack area, the address of this area varies depending on
the stack increase and decrease. That is, 10 extra bytes are consumed for the stack area used.
To Next Page
Loading...
Need help?
General
