
FLASHER 5 Manual 13
Error messages
The following error messages can occur during operation of FLASHER (shown in red on your PC) or re-
turned as errorlevel when operated from batch file and “Detailed errorlevel on return” option is set.
Code Error message Meaning / remedy
1
Erase failed
Erase operation has failed
2
Write failed
Write operation has failed
3
Verify failed
Verification failed. Loaded Program and contents of the flash-memory
are not identical.
4
Blank check failed
Chip is not blank
5
Flash write/erase
timed out
Could not write into flash memory, the max. waiting time has been
exceeded
6
Can not write into
this memory area
In serial mode, the boot area of Renesas CPUs can be read out, but
can not be written to.
7
Canceled
Last operation has been canceled by user.
21
Version read fail-
ure: Rx line prob-
lem ?
In serial mode, FLASHER reads out the version of Renesas target
CPUs bootloader. If this is not the right format (VER….), a read line
failure is most likely.
30
No ID
Renesas target CPU has no valid ID (This error should not occur)
31
ID mismatch
Renesas bootloader (target CPU) requires the correct ID. Without it,
you will be unable to access, read out, clear, or program the contents
of the flash memory. The requested ID depends on ID previously writ-
ten into the target CPU. For more information, please refer to the sec-
tion “ID code check function” of the CPUs users manual.
32
ID mismatch
Same as Error 31
40
Target chip says
"BUSY"
Renesas target chip has BUSY signal high (active). Most likely CPU did
not enter bootmode. Check all signals to target. Refer to CPUs users
manual about conditions to enter bootmode.
41
Target chip: Busy
does not react
Renesas target CPU should set BUSY after receiving the first bit or
byte (depending on CPU). Some possible reasons for this error:
a) RESET is not released
b) Target did not enter the serial I/O mode because conditions to enter
bootmode are not met. Check RESET, EPM, CE, CNVSS)
c) No clock (check with oscilloscope)
42
Target chip says
BUSY
Renesas target chip keep its Busy signal set (active) during communi-
cation. This inhibits communication between FLASHER and target.
Some possible reasons:
a) RESET is not released
b) Target did not enter the serial I/O mode because the signals applied
when RESET is released are not correct (EPM, CE, CNVSS)
c) No clock (check with oscilloscope)
43
Timeout of target
Target command Clear, Program or Verify could not be finished within
expected time. Please report this error.
55
CRC check in pro-
grammer failed.
Integrity of target data held in FLASHERs internal memory is lost.
Download new data to FLASHER.
56
Internal Vcc drop
during operation
A voltage drop on Flashers internal supply was detected. Internal data
may be damaged.
58
DAC for Vpp not
calibrated
FLASHER lost calibration data for Vpp generation circuit. Please return
FLASHER to factory, as calibration can not be done by user.
60
Unsupported inter-
face, check device
setting
FLASHER is requested to access a target CPU that is not supported by
Flasher. Normally this fault should not occur. Ensure that Flasher PC
software version fits to Flasher firmware version
61
Unsupported command
FLASHER received a command that is not supported. Ensure that
Flasher PC software version fits to Flasher firmware version.
62 No target data, please
download
FLASHER 5 never received valid data for target, therefore target can
not be programmed. Download target data.
63
FLASHER lost Setup
Setup data for Flasher invalid. Please run Option | Setup. and Option |
Device.
70
Illegal start byte
received
ST9 CPU did not send correct byte after reset release. Please check
target connection.
71
No start byte re-
ceived
ST9 target CPU did not send a Byte after reset release. Most likely ST9
CPU did not enter boot mode. Please check target connection.
72
No acknowledge re-
ceived
ST9 CPU did not send back acknowledge of command sent to RAM-
Code.
73
Target: communica-
tion timed out
ST9 target CPU did not send back data within expected time.
Kommentare zu diesen Handbüchern