M3A-2114G62 Renesas Electronics America, M3A-2114G62 Datasheet - Page 23

• Manufacturer Part Number: M3A-2114G62
• Description: DEV M32171 (MCU SOCKET TYPE) STA
• Manufacturer: Renesas Electronics America
• Type: MCUr

Specifications of M3A-2114G62

• Contents: Board, Serial Cable, C Compiler, Debugger, Programmer and Documentation
• For Use With/related Products: M32171
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant

3
(5) About hardware break
3.5.3 About Security Code Check Function
If the target microcomputer has security code stored in it, the dialog box shown in Figure 3.5-1 appears at
M3T-PD32RM (or M3S-KD32R) startup. When this dialog box is displayed, enter the appropriate security code. If the
security code you’ve entered does not match the stored security code, M3T-PD32RM (or M3S-KD32R) will not start
unless the contents of the internal flash memory are deleted.
Be sure to enter the security code that you set when writing to the flash memory.
Use the Format select button to choose the format of the security code you entered. Select the Save check box,
and the security code you entered is saved. From next time on, the security code saved here is used to check
matching with the stored security code when M3T- PD32RM (or M3S-KD32R) starts.
Debug functions of M3T-PD32RM (or M3S-KD32R) are realized by using the M32R core’s internal debug circuit
(SDI), and not by using the emulator’s hardware resources based on bus signals and debug information from the
MCU as in conventional emulators. The pre-execution PC break, post-execution PC break, and chip break all uses
this internal debug circuit (SDI).
Because the M3T-PD32RM (or M3S-KD32R) does not have trace pin information available as hardware resources,
the hardware break functions cannot be used that use the trace pins implemented in the M3T-PD32R-compatible
emulators.
Heed this point when referring to the PD32RM Help and PD32R Help.
Figure 3.5-1 Security Code Input Dialog Box
M3A-2114 User’s Manual (21/68)
Usage Precautions