Table of Contents
Advertisement
E2/E2 Lite
(2) Startup mode
When the emulator debugger is connected, handle the pins on the user system so that the startup mode
of the MCU is normal mode.
In normal mode, the MD pin is at the high level and the EHMD pin is at the low level. Correct connection
of the emulator debugger is not possible in energy harvesting startup mode or SCI/USB boot mode.
(3) Debugging after rewriting ID code
If the ID code (OSIS register) has been rewritten, enter the new ID code.
Here, the ID code to be entered means the value to be entered in [ID Code (Bytes)] under [Connection]
on the [Connection Settings] tabbed page (the operation is explained for the case when the e
use).
For example, when the following values have been secured, enter 00112233445566778899aabbccddeeff.
const unsigned long __OSISreg[4] = {
0x00112233,
0x44556677,
0x8899aabb,
0xccddeeff
};
(4) Entering the ALeRASE command for ID code
If an ALeRASE command is entered in [ID Code (Bytes)] under [Connection] on the [Connection Settings]
tabbed page, the code flash memory and option-setting memory will be erased when the emulator
debugger is connected.
For the conditions under which the ALeRASE command is usable, refer to the hardware manual for the
MCU you are using. If the ALeRASE command is entered then the emulator debugger is connected while
the command is not usable on the MCU, an error message "Failed to erase all flash memory by the ID for
erasing all flash memory." is displayed and the connection process is suspended.
R20UT4582EJ0100 Rev.1.00
Jul.16.19
Figure 3.4 Setting of [Hold reset during connect]
Figure 3.5 Setting of [ID Code (Bytes)]
Notes on Usage
2
studio is in
Page 21 of 30
Advertisement
Table of Contents
