Joined: 07 Jun 2006 Posts: 2087 Location: Odessa, Ukraine
Posted: Sun Oct 19, 2008 7:42 Post subject:
the 5352 doen not need /noreset, after eraseing the cfe, verify that it is erased by backing it up and looking at it with a hex editor. when flashing the cfe try using the switches
flash:cfe /noemw /bypass _________________ Want JTAG support - Donate a router
or Donate with PayPal !
Posted: Sun Oct 19, 2008 7:47 Post subject: tjtagv2-1-4 unstable!
Hello Buddies,
It looks that tjtagv2-1-4 is very unstable. Each time I backup CFE (WRT54GL v1.1, upgraded to DD-WRT v24 aleady) by issuing (under windows):
tjtagv2.exe -backup:cfe /noemw
I can always find several bytes different from last backup (using UltraEdit for binary comparsion).
While using HairyDairyMaid's original one:
wrt54g.exe -backup:cfe /noemw /fc:05
Then it is fine, and the file has no differece compared with CFE.bin obtained from Web GUI:
http://192.168.1.1/CFE.bin
Posted: Sun Oct 19, 2008 8:18 Post subject: Re: tjtagv2-1-4 unstable!
myacct wrote:
Hello Buddies,
It looks that tjtagv2-1-4 is very unstable. Each time I backup CFE (WRT54GL v1.1, upgraded to DD-WRT v24 aleady) by issuing (under windows):
tjtagv2.exe -backup:cfe /noemw
I can always find several bytes different from last backup (using UltraEdit for binary comparsion).
While using HairyDairyMaid's original one:
wrt54g.exe -backup:cfe /noemw /fc:05
Then it is fine, and the file has no differece compared with CFE.bin obtained from Web GUI:
http://192.168.1.1/CFE.bin
Oh, found the reason. The flash chip is EN29LV320B-70TCP, wrt54g.exe can not detect it and I have to add "/fc:05" which looks compatible. However, tjtagv2.exe does not prompt an error but I think it detects wrong chip. So I add "/fc:05" to tjtagv2.exe as well, and everything is fine.
Posted: Sun Oct 19, 2008 11:35 Post subject: Re: tjtagv2-1-4 unstable!
myacct wrote:
myacct wrote:
Hello Buddies,
It looks that tjtagv2-1-4 is very unstable. Each time I backup CFE (WRT54GL v1.1, upgraded to DD-WRT v24 aleady) by issuing (under windows):
tjtagv2.exe -backup:cfe /noemw
I can always find several bytes different from last backup (using UltraEdit for binary comparsion).
While using HairyDairyMaid's original one:
wrt54g.exe -backup:cfe /noemw /fc:05
Then it is fine, and the file has no differece compared with CFE.bin obtained from Web GUI:
http://192.168.1.1/CFE.bin
Oh, found the reason. The flash chip is EN29LV320B-70TCP, wrt54g.exe can not detect it and I have to add "/fc:05" which looks compatible. However, tjtagv2.exe does not prompt an error but I think it detects wrong chip. So I add "/fc:05" to tjtagv2.exe as well, and everything is fine.
Sorry, for tjtagv2.exe, you should append "/fc:80" (not "/fc:05") to select the chip.
Because the TopB and BotB definitions for that flash were swapped..
type tjtag alone, this will give you a list of all flash chips, find your flash chip:
*** Found a EON EN29LV320 2Mx16 BotB (4MB) Flash Chip ***
but choose the TopB chip /fc:81 instead of /fc:80...
That should take care of the problem, let me know if you test it ?
Thanks for the heads up, will be fixed in the next release
Thanks Tornado. I will test after work today.
What is difference between top-boot and bottom-boot? Can BCM5352 only support BotB flash chips, or both TopB and BotB chips can be supported? I am considering to upgrade the flash.
Another question, I notice that CFE starting at address "0x1FC00000" when using JTAG. If I solder the flash chip and use a certain programmer to write CFE.bin into the chip directly, should I just start from "0x00000000" or offset to "0x1FC00000"?
Joined: 07 Jun 2006 Posts: 2087 Location: Odessa, Ukraine
Posted: Mon Oct 20, 2008 7:18 Post subject:
myacct wrote:
Tornado wrote:
Because the TopB and BotB definitions for that flash were swapped..
type tjtag alone, this will give you a list of all flash chips, find your flash chip:
*** Found a EON EN29LV320 2Mx16 BotB (4MB) Flash Chip ***
but choose the TopB chip /fc:81 instead of /fc:80...
That should take care of the problem, let me know if you test it ?
Thanks for the heads up, will be fixed in the next release
Thanks Tornado. I will test after work today.
What is difference between top-boot and bottom-boot? Can BCM5352 only support BotB flash chips, or both TopB and BotB chips can be supported? I am considering to upgrade the flash.
Another question, I notice that CFE starting at address "0x1FC00000" when using JTAG. If I solder the flash chip and use a certain programmer to write CFE.bin into the chip directly, should I just start from "0x00000000" or offset to "0x1FC00000"?
1. the difference is where the smaller blocks are located, at the top or at the bottom:
8k blocks then 64k block for BotB
64k blocks then *k blocks for TopB
the 5352 doen not need /noreset, after eraseing the cfe, verify that it is erased by backing it up and looking at it with a hex editor. when flashing the cfe try using the switches
flash:cfe /noemw /bypass
The cfe is not erased and the data starts at address 2000 which is where it always stops at when trying to flash. So how do I get the data erased?
Because the TopB and BotB definitions for that flash were swapped..
type tjtag alone, this will give you a list of all flash chips, find your flash chip:
*** Found a EON EN29LV320 2Mx16 BotB (4MB) Flash Chip ***
but choose the TopB chip /fc:81 instead of /fc:80...
That should take care of the problem, let me know if you test it ?
Thanks for the heads up, will be fixed in the next release
I have made some more tests, and the result looks not determined by which command is used:
tjtagv2.exe -backup:cfe /noemw
tjtagv2.exe -backup:cfe /noemw /fc:80
tjtagv2.exe -backup:cfe /noemw /fc:81
It looks related to the status of the router (WRT54GL) itself. Sometimes when reading via JTAG, the power LED is always on (just like normal operation), and the backup result will be wrong (several bytes different). While sometimes the power LED is flashing (does it means that the router is reset?), and in this case the backup result is correct.