Solvline Eddy DKV2.1.0.3 - Manual (Page 117)

Chapter
9. Appendix
117
6) Start upgrade by double-clicking Eddy_burning_DataFlash.bat file. You need to wait
some time for seeing the log file after executing the batch file.
7) With the successful log message as below you can check the result of the upgrade.
If you cannot see the successful log message, you can refer to next chapter to fix the
problem.
8) With the successful log message, confirm whether the new firmware works properly
or not by rebooting Eddy DK v2.1 board.
9.2.6 Solving problems during Firmware Upgrade
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_DataFlash.bat or Eddy_burning_DataFlash.tcl files.
2) If your PC connects to Eddy-DK/S4M-DK board wrongly, log file will pop up as
below. In this case, you need to check the connection.
…
u-boot file: eddy-bl-2.1.0.1.bin
…
GENERIC::SendFile ./eddy-bs-2.1.0.1.bin at address 0x0
…
GENERIC::SendFile eddy-os-2.1.0.1.bin at address 0x3FF00
…
-I- === Load the linux file system ===
-I- Send File eddy-fs-2.1.0.1.bin at address 0x0025D580
GENERIC::SendFile eddy-fs-2.1.0.1.bin at address 0x25D580
…
script file : Eddy_burning_DataFlash.tcl
u-boot file: eddy-bl-2.1.0.1.bin
-E- Script File Eddy_burning_DataFlash.tcl returned error :
could not read "eddy-bl-
2.1.0.1.bin": no such file or directory - could not read "eddy-bl-2.1.0.1.bin": no such file
or directory
while executing
"file size $ubootFileName"
invoked from within