Sorry for the trouble. Please make sure if the SYS led of slave board flashes or not.
If the SYS led is off, i think the file system of slave board is broken. We need an USB-TTL cable to bring it up. Please prepare an USB-TTL cable and follow the manual to flash system firmware:
www.openvox.cn/pub/misc/tools/Flash%20Vo...0USB-TTL%20cable.pdf
If you need any help, you can add my skype for contact. My skype: This email address is being protected from spambots. You need JavaScript enabled to view it.
5 years 10 months ago - 5 years 10 months ago#11616by hexus
And another question
1.I found version of *.IMG firmware, other images are *.BIN. Can i use Bin images for flashing my device ?
2. In attached instruction
Notice:
Check “rootmtdblock=/dev/mtdblockX” filed, if it shows “mtdblock6”, then execute “update
second” to flash firmware; if “mtdblock4”, then execute “update first”.
BUT my print says something like
rootmtdblock=/dev/ubiblk0_0
What command should i use for update ?
1) You can only flash .img firmware.
2) Here are the commands you need if rootmtdblock=/dev/ubiblk0_0 :
setenv ipaddr XXXXX
setenv serverip XXXXX
setenv fsfile wg400-current.img
setenv rootmtdblock /dev/mtdblock4
run updatefirst
Hi, my board fails after update, and when i connect ttl there is only this strings in console
DDR Training.............................................................Done
eeprom-boot $Version: eeprom-boot_1_00_1
Autoboot from NAND in 1 seconds
Comcerto-1000 >
i can't input anything in console
i have working board, with 2 winbond flash chips (one on c1000_cpu_bd, and other in gsm_m35bd), which of them i need to read and write to the bricked board, what memory blocks i need to write?