E2, IE850A
5. Notes on Usage
R20UT4140EJ0300 Rev.3.00
Page 26 of 41
Oct.09.20
5.2
Notes on connecting the emulator
5.2.1
Entering the ID code
To start debugging after the emulator has been connected, the OCDID, customer ID, and data flash ID must
be authenticated. Authentication of other ID codes may also be required (refer to section 5.4.3).
Enter the ID codes that have been set in the Security Settings area in the following order from the debugger
when the emulator is connected.
ID7 (ID[255:224]), ID6 (ID[223:192]), ID5 (ID[191:160]), ID4 (ID[159,128]),
ID3 (ID[127:96]), ID2 (ID[95:64]), ID1 (ID[63:32]), ID0 (ID[31:0])
The ID codes that have been set in the Security Settings area matching those entered from the debugger
means success in authentication, so debugging can be started.
IDs of the target device are written in debuggers as shown below.
ID of the Target Device
Notation for CS+
Notation for MULTI
OCD ID
OCD ID
-id
Customer ID
Customer ID
-csid
Data Flash ID
Data Flash ID
-dfid
Serial Programmer ID
Serial Programmer ID
-spid
C-TEST ID
C-TEST ID
-ctid
RHSIF ID
ID0
-optid
5.2.2
Setting of the OIDDIS bit of S_OPBT0
It is not possible to start debugging if the setting of the OIDDIS bit of S_OPBT0 is 0 (disabling ID
authentication).
5.2.3
Setting of the MOSC_40MHz bit of OPBT7
Set the MOSC_40MHz bit of OPBT7 according to the input frequency of the main OSC. The initial value of the
MOSC_40MHz bit is 1 (40 MHz).
When the input frequency of the main OSC is 20 MHz, set the MOSC_40MHz bit to 0 (20 MHz) by the
Renesas Flash Programmer (RFP).
5.2.4
Cases where connecting the debugger is not possible
It is not possible to start debugging if the target device is in any of the following states (this also applies in
cases where hot plug-in connection is in use).
•
Reset input state (except for a reset input from the emulator)
•
Power off standby mode
