Posted: Mon Oct 26, 2009 15:10 Post subject: eoc 5610 flashing problem from firmware 1.1.12
Hi,
Like to buy an activation password. So I followed the prcedure to first try. It wouldn't load the linux.bin file error after 94% using Tftp32. I got:
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .
The numbers are quite different from the ones in the stickys. I am upgrading from 1.1.12. Brainslayer, Sash, any idea? The LAN led works well and I can boot redboot. Just can't have it to loa the bin file?
Any idea?
Thanks
Hi, did you follow the procedure till the end ? It also takes around 10-15 minutes to have it done, so dont interrupt the transfer at that moment. JUST WAIT !
Also, which version are you trying to load ? I had to load the 13064 twice, in order to have it working.
Cheers, Michel _________________ 2x EOC-2160 - AP 2x14dB Yagy to 450m link
2x EOC-2160 - RP 2x17dB Panels - 2x 7Mbps
1x WRT54G v2.2 - V24-SP2 13577VPN Eko
All Senao EOC-2610 V1.10 Std 15362 BS
1x UBNT Bullet 2 - RP 18dB Panel - 11Mbps - 13Km link
Also I am not an expert and I might be totally wrong but it seems as if there was not enough space in memory to write the file, as if it starting to close to the end (again those numbers)?
Bayoule
Coming back after checking power and chnging cables. Still not loading. Is this 15mn for loading or for fis create linux cos mine simply not loading? Any other ideas? Thanks
Joined: 10 Aug 2009 Posts: 42 Location: Michigan, USA
Posted: Fri Oct 30, 2009 2:15 Post subject:
Same exact issue. EOC-5610 locks up at 94% download.
same memory values too
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .
Are we sure load -r -b 0x80041000 linux.bin is the right command... could the starting memory location be different?
I should mention my beginning firware was 1.1.07 and not 1.1.12 as the original posters was. _________________ EOC-5610 -dd-wrt soon....
WRT54g-tm -Mega Build
WRT350n -Mega Build, w/ ext antennas
Joined: 10 Aug 2009 Posts: 42 Location: Michigan, USA
Posted: Fri Oct 30, 2009 2:32 Post subject:
after a little bit of common sense....
Since build 13064 seemed to be a little too big. I looked at build 12533
build 12533 is roughly 2mb smaller than build 13064.
I followed the directions but this time used 12533, everything went off without a hitch!
Someone might want to look at the bin listed for the EOC-5610 it looks like build 13064 might be bad? _________________ EOC-5610 -dd-wrt soon....
WRT54g-tm -Mega Build
WRT350n -Mega Build, w/ ext antennas
OK I was able to load 12533 like Techtravis. I bought the activation code too. Now I am afraid to upgrade through web for 13064? Should I wait for the next release? Thanks
Bayoule
Joined: 06 Jun 2006 Posts: 3763 Location: I'm the one on the plate.
Posted: Tue Nov 03, 2009 22:48 Post subject:
bayoule wrote:
OK I was able to load 12533 like Techtravis. I bought the activation code too. Now I am afraid to upgrade through web for 13064? Should I wait for the next release? Thanks
Bayoule
Is there a particular reason for your burning desire to stay at the cutting edge of this beta firmware development and endure the punishment of on-going de-bugging ?
Is there a specific feature or functinality in the newest revision that you are after ? I would love to know.
Joined: 10 Aug 2009 Posts: 42 Location: Michigan, USA
Posted: Wed Nov 04, 2009 6:49 Post subject:
In retrospect I wish I hadn't upgraded :)
I know if the next router has the same symptoms (will load 12533 and not 13064 through redboot) I won't even attempt 13064.
It wouldn't be sure a big deal if they included a JTAG port on the damn thing. _________________ EOC-5610 -dd-wrt soon....
WRT54g-tm -Mega Build
WRT350n -Mega Build, w/ ext antennas