Action For Error - Renesas MINICUBE QB-MINI2 User Manual

CHAPTER 5 OCD CHECK FOR MINICUBE2 AND 78K0S MICROCONTROLLER
[Log file]
Execution time Execution time
Reset status = OK Reset status = OK
Hardware version Hardware version
Error indication Error indication
In this NG example, the error "Program Download" is detected.
An error during flash memory programming is detected. The cause is an error in pin connection on the board
for connecting MINICUBE2 on the target system (pin 5 (SO) is shorted with GND).
5.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 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.
2 Log file write error
The specified log file cannot be accessed.
→ Confirm that the folder, path, and file are write-enabled.
3 Monitor Command(xxH) Error
Communication between the target device and MINICUBE2 has failed.
→ The cause may be a problem in the electrical specifications of the cable or the target system, or the USB
driver may not be operating normally.
Confirm the connection and restart Windows on the host machine.
30
tt:mm:ss tt:mm:ss
Target Reset: HIGH Target Reset: HIGH
MINICUBE2 4100 x xx.xx MINICUBE2 4100 x xx.xx
Program Download:NG Program Download:NG
Emulator Test End Emulator Test End
User's Manual U18591EJ2V0UM
(1/2)