RL78/G15 CHAPTER 20 ON-CHIP DEBUG FUNCTION
R01UH0959EJ0110 Rev.1.10 Page 687 of 765
Mar 7, 2023
20.4 Securing of User Resources
To perform communication between the RL78 microcontroller and E2, E2 Lite 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 link options.
1) Securement of memory space
The shaded portions in Figure 20-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 20-3. Memory Spaces Where Debug Monitor Programs Are Allocated
Security ID area
(
10 bytes)
Note 2
Debug monitor area
(10 bytes
)
Debug monitor area
(2 bytes
)
On
-chip debug option byte
area
(1 byte)
: Area used for on
-chip debugging
Note
1
000D8H
000CEH
000C4H
000C3H
00002H
00000H
Code
flash area
Code flash memory
Use prohibited
SFR area
4 bytes
Note 3
Stack area for debugging
(
10
bytes)
Note 4
Mirror area
Internal
RAM area
Internal RAM
Note 1. Address differs depending on products as follows.
Products Address
R5F12067, R5F12047, R5F12017, R5F12007 00FFFH
R5F12068, R5F12048, R5F12018, R5F12008 01FFFH
Note 2. In debugging, reset vector is rewritten to address allocated to a monitor program.
Note 3. When the pseudo-RRM function and the pseudo-DMM function are used, four bytes in the RAM area are
consumed.
The RAM area is set by the build tool, when the pseudo-RRM function and the pseudo-DMM function are
used.
If the RAM area has not been set, the first four bytes of the RAM area will be used.
(For details on the setting, refer to the user's manual of the build tool.)
When the pseudo-RRM function and pseudo-DMM function are not used, this area can be used as the
internal RAM.
To Next Page
Loading...
Need help?
General
