mikasi
New Member
I have Linksys WRT54GS v4.0 router that I would like to bring back to life after bricking it while unsuccessfully tried to upgrade OpenWrt firmware.
For that purpose I've bought FlashcatUSB v1.8 board since I was sure, according to good reviews, that there will be no problems doing that.
But, as I am apparently not that fortunate, there are problems...
1.) As instructed by manual I have flashed FlashcatUSB with FCUSB.7.05.EJTAG_32K.hex firmware first.
2.) Then I have connected FlashcatUSB to the JTAG header pins
3.) After restarting FlashcatUSB application a wrong version detection of WRT54GS router was made (version with 2 MB of flash was detected instead of the one with 4 MB of flash). For that I have adapted Autorun.ini file to load my own JTAG script file named WRT54GS_4M_JTAG.bcs which I derived from WRT54GS_2M_JTAG.bcs.
4.) From now on I am able to read all parts of software CFE, Kernel and NVRAM, but not able to write anything back, not even the binary that was read only a minute ago.
Looking at the FlashcatUSB console output I assume there must be something wrong with the CFI memory initialization.
Initialization ...
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 202
Welcome to FlashcatUSB interfacing software, build: 330
Running on: Microsoft Windows 7 Ultimate (32 bit)
Initializing EJTAG engine
Device connected in JTAG mode: 7,05
JTAG: IR length set to 8
JTAG engine setup successfully
Detected CPU ID: 0x535217F IMP CODE: 0x800904
Manufacturer ID: 0xBF Part ID: 0x5352
EJTAG Version support: 2.0
Target device supports DMA mode
Checking for a device specific script to automatically load
Loading device specific script: WRT54GS_4M_JTAG.bcs
Loading script: WRT54GS_4M_JTAG.bcs
Setting device parameter (Intel Flash delay) to 0x32
Setting device parameter (AMD Flash delay) to 0xC8
Setting device parameter (Memory Read Delay) to 0x32
MemoryInit: Failed - device parameters failed Init
I suppose CFI device initialization should look something like the one on http://blackcatusb.net/index.php?threads/linksys-wrt54gs_2m.79/ where flash description is clearly indicated.
Reading NVRAM is somewhat successful I guess ...
Button Hander::Calling Event: ReadNVRAM
Beginning memory read from DRAM
Start address: 536805376 (0x1FFF0000) Length: 65536
Read operation complete
Read 65536 bytes in 0,794 seconds, 82.852 Bytes/s
Beginning memory read from DRAM
Start address: 536805376 (0x1FFF0000) Length: 65536
Read operation complete
Read 65536 bytes in 0,794 seconds, 82.852 Bytes/s
Data saved. 65536 bytes written
Button Hander::Calling Event: Done
But writing the same NVRAM back is not successful ...
Button Hander::Calling Event: WriteNVRAM
Unable to write data to flash device (out of bounds)
Canceled memory write operation
Button Hander::Calling Event: Done
My flash device is Intel TE28F320C3BD90 and should be supported according to the device list on http://blackcatusb.net/index.php?threads/supported-flashes.1/.
I am completely baffled and do not know what to do next. If you have any clue on how to adapt my JTAG script file and/or do something else to be successful the please let me know.
Best regards,
Mitja
For that purpose I've bought FlashcatUSB v1.8 board since I was sure, according to good reviews, that there will be no problems doing that.
But, as I am apparently not that fortunate, there are problems...
1.) As instructed by manual I have flashed FlashcatUSB with FCUSB.7.05.EJTAG_32K.hex firmware first.
2.) Then I have connected FlashcatUSB to the JTAG header pins
3.) After restarting FlashcatUSB application a wrong version detection of WRT54GS router was made (version with 2 MB of flash was detected instead of the one with 4 MB of flash). For that I have adapted Autorun.ini file to load my own JTAG script file named WRT54GS_4M_JTAG.bcs which I derived from WRT54GS_2M_JTAG.bcs.
4.) From now on I am able to read all parts of software CFE, Kernel and NVRAM, but not able to write anything back, not even the binary that was read only a minute ago.
Looking at the FlashcatUSB console output I assume there must be something wrong with the CFI memory initialization.
Initialization ...
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 202
Welcome to FlashcatUSB interfacing software, build: 330
Running on: Microsoft Windows 7 Ultimate (32 bit)
Initializing EJTAG engine
Device connected in JTAG mode: 7,05
JTAG: IR length set to 8
JTAG engine setup successfully
Detected CPU ID: 0x535217F IMP CODE: 0x800904
Manufacturer ID: 0xBF Part ID: 0x5352
EJTAG Version support: 2.0
Target device supports DMA mode
Checking for a device specific script to automatically load
Loading device specific script: WRT54GS_4M_JTAG.bcs
Loading script: WRT54GS_4M_JTAG.bcs
Setting device parameter (Intel Flash delay) to 0x32
Setting device parameter (AMD Flash delay) to 0xC8
Setting device parameter (Memory Read Delay) to 0x32
MemoryInit: Failed - device parameters failed Init
I suppose CFI device initialization should look something like the one on http://blackcatusb.net/index.php?threads/linksys-wrt54gs_2m.79/ where flash description is clearly indicated.
Reading NVRAM is somewhat successful I guess ...
Button Hander::Calling Event: ReadNVRAM
Beginning memory read from DRAM
Start address: 536805376 (0x1FFF0000) Length: 65536
Read operation complete
Read 65536 bytes in 0,794 seconds, 82.852 Bytes/s
Beginning memory read from DRAM
Start address: 536805376 (0x1FFF0000) Length: 65536
Read operation complete
Read 65536 bytes in 0,794 seconds, 82.852 Bytes/s
Data saved. 65536 bytes written
Button Hander::Calling Event: Done
But writing the same NVRAM back is not successful ...
Button Hander::Calling Event: WriteNVRAM
Unable to write data to flash device (out of bounds)
Canceled memory write operation
Button Hander::Calling Event: Done
My flash device is Intel TE28F320C3BD90 and should be supported according to the device list on http://blackcatusb.net/index.php?threads/supported-flashes.1/.
I am completely baffled and do not know what to do next. If you have any clue on how to adapt my JTAG script file and/or do something else to be successful the please let me know.
Best regards,
Mitja