Table of Contents
Advertisement
CHAPTER
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.
When a partner tool is used, read also the following material.
When using MULTI manufactured by Green Hills Software
QB-MINI2 Setup Manual User's Manual Partner Tool (U19158E)
When using C-SPY
IAR C-SPY Hardware Debugger Systems User Guide issued by IAR Systems
•
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.
Internal ROM space
2 KB
4 bytes
10 bytes
4 bytes
4 bytes
: Debugging area
Note The vectors for the receive error interrupt or receive status interrupt, if any, must be secured.
•
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.
32
3
HOW TO USE MINICUBE2 WITH V850 MICROCONTROLLER
TM
manufactured by IAR Systems
Memory Spaces Where Debug Monitor Programs Are Allocated
Internal ROM end address
CSI or UART eceive interrupt vector
0x70 (security ID area)
0x60 (interrupt vector for debugging)
0x0 (reset vector)
User's Manual
Internal RAM space
10 to 16 bytes
Note
U18371EJ5V0UM
Internal RAM end address
Advertisement
Table of Contents
