Table of Contents
Advertisement
CHAPTER 3 OCD CHECK FOR MINICUBE2 AND 78K0 MICROCONTROLLER
3.4
Action for Error
The errors that may occur during self-testing (such as setting error) and relevant actions for coping with the errors
are listed below.
If an error other than below is displayed, the cause may be a defect in MINICUBE2. If the same error is displayed
even after the relevant action is implemented, the cause may be a defect in MINICUBE2. In such a case, consult an
NEC Electronics sales representative or distributor.
No.
Error message and action
1
Communication error
There is no response from the target device.
→ Address 0x84 (on-chip debug emulator use enable flag) is set to 0x00 (disable use) or the target system and
MINICUBE2 are not connected correctly.
Confirm the file of the program written to the target device and connection between the target system and
MINICUBE2.
2
Target Power : 0.0V [NG]
The power supply to the target system cannot be detected.
→ Confirm that the power for the target system is on.
→ Check the connection between the target system and MINICUBE2
3
78K0 OCD board is not connected
The 78K0-OCD board is not connected.
→ Confirm that the 78K0-OCD board is connected.
4
Target Clock: 0.00MHz [NG]
The clock mounted in the CLK1 socket may not be operating.
→ Confirm the clock oscillation, or remove the clock mounted in the CLK1 socket in the 78K0-OCD board and
use the internal clock.
5
Select Socket Clock
The clock mounted in the CLK1 socket is not selected.
→ Select "socket" for the clock setting, or remove the clock mounted in the CLK1 socket and select "internal".
6
Driver open error
(1) There is no response from MINICUBE2.
→ Check the connections between the host machine and the USB cable, and the USB cable and the
MINICUBE2.
→ Turn all the power supplies off according to the procedures described in the user's manual. (MINICUBE2 is
turned off by disconnecting the USB cable.)
Turn all the power supplies on, and then click the [Test] button.
If an error message is displayed even after taking these measures, restart Windows on the host machine
before turning all the power supplies on.
(2) The debugger has been started.
→ The debugger and the OCD Checker cannot be started simultaneously, so terminate the debugger.
(3) The USB driver may not be operating normally.
→ Confirm the cable connection and the USB driver setup. Re-install the USB driver as necessary.
(4) The debugger may not be installed normally.
→ Re-install the debugger.
18
User's Manual U18591EJ2V0UM
(1/2)
Advertisement
Table of Contents
