
HOKUTO DENSHI
CO;LTD;
FLASH2
株式会社
16
LED Status of FLASH2 and Trouble Shootings
Programming Flow
LED Status and Frequently Occurred Troubles
Connection and Power on
DC supply into FLASH2, then Target
board power on.
Start of Writing
Click Start
or push
F6
Turn off
→
All LED do not light.
User Vcc
ERR
ERASE
WRITE
TXD
RXD
Ready
→
Only USER VCC lights.
User Vcc
ERR
ERASE
WRITE
TXD
RXD
¶
UserVcc LED does not light.
Check Power supply to FLASH2 and the target board.
Especially, be careful about the dry cell
’s power level.
We recommend the new ones to ensure the writing.
Starting boot mode
Bit rate adjusting, and erasing
all data
→
USER VCC, ERASE and WRITE light. TXD and RXD are blinking.
User Vcc
ERR
ERASE
WRITE
TXD
RXD
¶
“#6 Can't start in the boot mode.” is appeared, and stopped.
No signal reached the target MCU.
Communications are disturbed by RS232C cable
misuse/breaking/contact
failure,
or
FLASH2
breakdown. Sometimes Windows operations have
some troubles in its environment. Check the
RS232C cable, and also check the signals correctly
transferring from the FLASH2_17 and controlling of
1/3/5/7/9/11/13 at its target interface. If some signals
are uncontrolled correctly, error must be occurred
before FLASH2 output.
No answer from the target MCU.
In spite of the correct communications from FLASH2, the target MCU makes no reply. Check
the circuit around the MCU in writing, especially the port MD/FWE/RESET and SCI port are
controlled correctly. Sometimes, Xtal oscillation failures influence in transferring.
¶
#6 Some Error occurred in progress.
As acceptable transmission error ratio in serial communications, less than 0.16% is
recommended. If transmission is successes on border at first, error can be occurred in
progress. Unsoldered MCU pins or program reset like
“WDT” also disturb transmission
progress.
¶
“#7 Can't Erase Flash memory.” is appeared, and stopped.
MCU does not reply correct H
’AA, although the first part of transmission is succeeded.
Check the correct MCU type name is selected, communication Failure by noise or Xtal
oscillation failures. Transferring rate combination change is sometimes effective. Unsoldered
MCU pins or program reset like
“WDT” also disturb transmission progress.
On writing
Bit rate optimizing at
maximum rate.
Transferring user program in
prescribed block size and
compare.
(Verifying in option)
→
USER VCC and WRITE light. TXD and RXD are blinking.
User Vcc
ERR
ERASE
WRITE
TXD
RXD
¶
Communications Errors are often occurred.
Communication state is influenced by cable breaking/defects/misuse. The cable length for
the target cable is guaranteed in the attached one, 30 cm in max. Power supply is also
important, especially in the case of the dry cells. Check the voltage and the UserVcc LED
status. When transmissions failure is often occurred in specified address, check the port
status of the target to examine the wandering in processing.
¶
Optional Verify is failed.
Guaranteed programming by Hitachi is finished except this optional verify.
Optional verify is
sometimes omit the correct ones.
Completing of writing
Completed
correctly
→
Only USER VCC lights.
User Vcc
ERR
ERASE
WRITE
TXD
RXD
Error occured
※
ERR LED does not distinguish
until starting next writing.
→
USER VCC and ERR light.
User Vcc
ERR
ERASE
WRITE
TXD
RXD
Test point by
Oscilloscope