Eddy DK Programmer Guide
140
9.2.4
Solving problems during System recovery execution via USB
1)
If you use firmware file name wrongly, log file will pop up as below.In this case, you should check whether the
file names of firmware copied is same with the firmware names in Eddy_burning_xxxxFlash.bat or
Eddy_burning_xxxxFlash.tcl files.
2)
If your PC connects to Eddy-DK board wrongly, log file will pop up as below. In this case, you need to check
the connection.
3)
If you get as below log file, you need to check the S6 dip switch. It should be pulled up.
…
script file : Eddy_burning_xxxxFlash.tcl
u-boot file: eddy-bl-2.x.x.x.bin
-E- Script File Eddy_burning_xxxxFlash.tcl returned error :
could not read "eddy-bl-
2.x.x.x.bin": no such file or directory - could not read "eddy-bl-2.x.x.x.bin": no such file or
directory
while executing
"file size $ubootFileName"
invoked from within
-I- Waiting ...
-E-
Connection \usb\ARM0 not found
-E- Connection list : COM2 COM3 COM4 COM5
…
-I- Loading applet isp-dataflash-at91sam9g20.bin at address 0x20000000
-E- Script File Eddy_burning_DataFlash.tcl returned error : Error Initializing xxxxFlash Applet
(Can't detect known device) - Error Initializing xxxxFlash Applet (Can't detect known device)
while executing
"error "Error Initializing xxxxFlash Applet ($dummy_err)""
(procedure "xxxxFLASH::Init" line 13)
invoked from within
"xxxxFLASH::Init 1 "
