CHAPTER 6 HOW TO USE MINICUBE2 WITH 78K0R MICROCONTROLLER
User’s Manual U18371EJ1V0UM
146
6.2.5 Securing of user resources and setting of security ID and on-chip debug option byte
The user must prepare the following to perform communication between MINICUBE2 and the target device and
implement each debug function. If NEC Electronics assembler RA78K0R or compiler CC78K0R is used, the
items can be set by using linker options. Refer to the descriptions on the following pages and set these items.
• Securement of memory space
The shaded portions in Figure 6-11 are the areas reserved for placing the debug monitor program, so user
programs or data cannot be allocated in these spaces. 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 6-11. Memory Spaces Where Debug Monitor Programs Are Allocated
1024 bytes
10 bytes
2 bytes
10 bytes
1 byte
C4H
D7H
C3H (b) On-chip debug option byte area
Internal ROM space
Internal ROM end address
6 bytes
Internal RAM space
Internal RAM end address
(d) Stack area for debugging
CDH
(a) Debug monitor area
D8H
CEH
(c) Security ID area
(a) Debug monitor area
: Area used for on-chip debugging
03H
02H
(a) Debug monitor area
1024 bytes
10 bytes
2 bytes
10 bytes
1 byte
C4H
D7H
C3H (b) On-chip debug option byte area
Internal ROM space
Internal ROM end address
6 bytes
Internal RAM space
Internal RAM end address
(d) Stack area for debugging
CDH
(a) Debug monitor area
D8H
CEH
(c) Security ID area
(a) Debug monitor area
: Area used for on-chip debugging
03H
02H
(a) Debug monitor area
Note
In debugging, reset vector is rewritten
to address allocated to a monitor
program.
• Setting of security ID and on-chip debug option byte
The security ID or on-chip debug option byte must be embedded in the area filled with yellow (0xC3 and
0xC4 to 0xCD) in Figure 6-11, to prevent the memory from being read by an unauthorized person.
Note
