Filter
Top Products
( 45 / 54 )
6.2 When an Error Message "Cannot be reset" is Displayed
When an error message "Target MCU cannot be reset. Reset the target system." is displayed at the
time of starting up the M3T-PD38, check the following:
(1) The firmware does not match the emulation pod used.
Are the firmware names conforming to the emulation pod (see the manual for details) written
in the MCU file? If the emulator debugger shows an instruction for downloading the firmware
when it started up, download the firmware that matches the emulation pod according to the
displayed message.
(2) The contents of the MCU file are different.
After consulting the user's manual of your emulator debugger, correct the contents of the MCU
file with a text editor.
(3) Is an incorrect MCU file selected?
From the Init dialog box that is displayed when M3T-PD38 starts, select the correct MCU file
that suits the emulator MCU used.
(4) Is the target system supplied with the correct power, clock, and reset?
Power supply voltage: Check whether it is within the rated voltage range of the emulation
pod and MCU.
Clock: Check whether the clock is oscillating correctly.
Reset: a) If the reset circuit of the target system has a watchdog timer
function, disable the watchdog timer function while using the
emulator.
b) When the reset circuit on the target is an H-output type RESET IC:
When debugging with M38000TL2-FPD, use either an open-drain
type reset IC or a CR reset circuit. The recommended pull-up value
is about 10kΩ. The MCU can be reset by outputting "L" to the
target through the reset clip on the M38000TL2-FPD. However, if
the reset circuit on the target is an H-output type RESET IC, it
cannot be set to "L" and the emulator will not operate properly.
(5) Because the emulator main unit, emulation pod, emulator MCU, and target system are not
firmly connected, imperfect contact exists in one of these connections. Connect these pieces
of equipment firmly again.
(6) Check to see if the GND and RESET cables from the M38000TL2-FPD are correctly
connected to the target system.
(7) If none of the above holds true, the hardware or the emulator MCU may be faulty. Please
contact your local distributor.