CHAPTER 3 HOW TO USE MINICUBE2 WITH V850 MICROCONTROLLER
User’s Manual U18371EJ1V0UM
32
3.2.5 Securing of user resources and setting of security ID
The user must prepare the following to perform communication between MINICUBE2 and the target device and
implement each debug function. Refer to the descriptions on the following pages and set these items in the user
program or using the compiler options.
• Securement of memory space
The shaded portions in Figure 3-12 are the areas reserved for placing the debug monitor program, so user
programs and data cannot be allocated in these spaces. These spaces must be secured so as not to be used
by the user program.
Figure 3-12. Memory Spaces Where Debug Monitor Programs Are Allocated
4 bytes
0x0 (reset vector)
Internal ROM space
0x60 (interrupt vector for debugging)
0x70 (security ID area)
2 KB
10 bytes
4 bytes
4 bytes
10 to 16 bytes
Internal RAM space
Internal ROM end address
Internal RAM end address
: Debugging area
CSI or UART receive interrupt vector
4 bytes
0x0 (reset vector)
Internal ROM space
0x60 (interrupt vector for debugging)
0x70 (security ID area)
2 KB
10 bytes
4 bytes
4 bytes
10 to 16 bytes
Internal RAM space
Internal ROM end address
Internal RAM end address
: Debugging area
CSI or UART receive interrupt vector
• Securement of serial interface for communication
The register settings, concerning UART or CSI-H/S used for communication between MINICUBE2 and the
target device, performed by the debug monitor program must not be changed.
• Security ID setting
The ID code must be embedded in the area filled with yellow (0x70 to 0x79) in Figure 3-12, to prevent the
memory from being read by an unauthorized person.
