Page 1 of 2
Dead Fonera 2200?
Posted: Sat Jan 29, 2011 4:10 pm
by registar
I just tried to flash my fonera!
I downloaded the last FonFlash utility, gargoyle_1.3.9-atheros-vmlinux and gargoyle_1.3.9-atheros-root.squashfs and everything went OK. At the end appeared a message saying my device was flashed.
I reboot the fonera and tryed to login at 192.168.1.1 without success.
O noticed there is no green WLAN led!
What can I do? What went wrong?
help please
Re: Dead Fonera 2200?
Posted: Mon Jan 31, 2011 9:18 pm
by DoesItMatter
Did you connect to the wired port?
I don't remember if the WLAN is enabled by default.
Try to connect wired and see if you can access it.
You can always try and re-flash to see if it works.
Try a flash of 1.2.5 and see if that works also.
Re: Dead Fonera 2200?
Posted: Mon Mar 28, 2011 9:31 am
by gargfon
Hi, I have the same problem , I flashed my fonera2200 with last versions of gargoyle ,ddwrt and opewrt (flashfon-gui said successfully but i can't access the web or ssh interfaces).
It's reachable just on telnet at 192.168.1.1 and port 9000 (redboot). Can suggest me next step please to make it works ?
Thanks on advance .
Re: Dead Fonera 2200?
Posted: Fri Apr 01, 2011 5:44 am
by DoesItMatter
gargfon wrote:Hi, I have the same problem , I flashed my fonera2200 with last versions of gargoyle ,ddwrt and opewrt (flashfon-gui said successfully but i can't access the web or ssh interfaces).
It's reachable just on telnet at 192.168.1.1 and port 9000 (redboot). Can suggest me next step please to make it works ?
Thanks on advance .
What version of Gargoyle are you trying to flash?
I would suggest flashing 1.2.5 on the Fon 2200
That version should work well on the Fonera 2100/2200/2201's
I don't know if Wireless is enabled by default or not.
You might have to connect via the Ethernet port for initial setup.
Re: Dead Fonera 2200?
Posted: Fri Apr 01, 2011 10:51 am
by gargfon
Hi DoesItMatter, thanks for your reply. I flashed successfull it once and worked fine for almost 6months with gargoyle v1.3.5.
A day I turn it on and doesnt work then i flashed with 1.3.12 , 1.3.15 ,again with 1.3.5 but still the same : the flashing process ends with success (fonflash) but the web interface is not available and it stops on redboot, on port 9000.
I do all the process with ethernet cable and tried other wrt-based firmware but still same result
.
Any clue to make it works again ?
Thanks.
Re: Dead Fonera 2200?
Posted: Fri Apr 01, 2011 12:23 pm
by DoesItMatter
Telnet into Redboot
Run this command
fis init -f
That should completely initialize and wipe the flash chip
WATCH the output. I had a Fon 2201 die because the flash chip
started to have errors reported on it. I guess it was going bad.
If you see errors reported on the fis command, your flash chip
may be dying and might have to look for another router.
Re: Dead Fonera 2200?
Posted: Fri Apr 01, 2011 12:30 pm
by juzis28
I successfully flashed v 1.3.13 to my fonera 2200 over serial console. And seem this is most stable build i ever tried.
There was only one thing to edit: calculate lengh of the rootfs.
Here are steps i performed
- Connect ttl serial cable (info here). (Also you can order cheap usb to ttl converter dongle on ebay...)
- Start putty (or hyper terminal) and open console. Terminal connection as described 1 step (link), 9600-8-N-1 and no flow control. Power up fonera and press ctrl+c (^C) when offered, go to the RedBoot.
- Fire up tftp32 server and upload kernel image to fonera
Code: Select all
load -r -b %{FREEMEMLO} gargoyle_1.3.13-atheros-vmlinux.lzma
- Delete old images:
- create new kernel:
Code: Select all
fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7
- Check the free space available
and get offset:
- Substract the first from second and you get lengh offset you will use to create rootfs:
(you will use it as 0x006E0000 in step 9)
- Now load the root filesystem to the box:
Code: Select all
load -r -b %{FREEMEMLO} gargoyle_1.3.13-atheros-root.squashfs
- Create the partition for it (use offset you got in step 7):
- Check if config does not contain errors:
- Boot fonera with new firmware:
OR
- Reboot fonera...
With this howto i flashed 2 foneras without any problems many times.
Gargoyle works well, thank you for great job!
Re: Dead Fonera 2200?
Posted: Fri Apr 01, 2011 1:08 pm
by gargfon
Thanks both of you !
@juzi28 Thanks for you procedure , i save it for last since i don't have a serial cable so need to look for one or build one on my own. It's not clear for me , sorry i'm a newbie
, the memory addresses you wrote are valid just for gargoyle v.13 or also for other versions ?
@DoesItMatter Thanks for the command, it went well at least hope so
here the log :
Code: Select all
RedBoot> fis init -f
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xa8030000-0xa87e0000: ...........................................................................................................................
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
Can you please list me whole procedure step by step ? I found many guides in the net but i don't know which one is good for my situation.
My fonera is still on and ready for your commands , Master :p
Thanks.
Re: Dead Fonera 2200?
Posted: Fri Apr 01, 2011 1:59 pm
by juzis28
memory adresses are valid for my fonera, it is not gargoyle related. You could flash openwrt as well according my short how to.
I saw in the internet few different manuals for fonera re-flashing and here are different addresses. but addresses for kernel are always the same, differs only rootfs address.
I connected the cable to serial port, but you`ve RedBot enabled telnet. It is the same (almost).
Re: Dead Fonera 2200?
Posted: Sat Apr 02, 2011 9:55 am
by gargfon
Thanks juzis28 !!!
I got it working again now , born again fon with gargoyle_1.3.13
If necessary I would suggest to upgrade the wiki section.
For ethernet redboot procedure you just need to set a static ip.
I noticed fon telnet address changed since last time I tried from 192.168.1.254 to 192.168.1.1
I got a few errors , wishing It's not serious problem on the device :
Code: Select all
RedBoot> fis init -f
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000001
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000555
I came ahead and successfully completed the flash process.
Thanks to juzis28, DoesItMatter for helping and gargoyle guys :p and openwrt team for these great systems.
PS: I add the full log of my operation:) :
Code: Select all
telnet 192.168.1.1 9000
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
== Executing boot script in 1.990 seconds - enter ^C to abort
RedBoot> No image 'vmlinux.bin.l7' found
RedBoot> Can't execute Linux - invalid entry address
RedBoot> ip_address -l 192.168.1.1/24 -h 192.168.1.3
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.3
RedBoot> load -r -b %{FREEMEMLO} gargoyle_1.3.13-atheros-vmlinux.lzma
Using default protocol (TFTP)
Raw file loaded 0x80040c00-0x80110bff, assumed entry at 0x80040c00
RedBoot> fis init -f
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000001
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000555
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xa8030000-0xa87e0000: ...........................................................................................................................
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7
Erase from 0xa8030000-0xa8100000: .............
... Program from 0x80040c00-0x80110c00 at 0xa8030000: .............
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot>fis free
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000001
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
0xA8100000 .. 0xA87E0000
RedBoot> load -r -b %{FREEMEMLO} gargoyle_1.3.13-atheros-root.squashfs
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
Using default protocol (TFTP)
Raw file loaded 0x80040c00-0x80300bff, assumed entry at 0x80040c00
RedBoot> fis create -l 0x006E0000 rootfs
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000145
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
... Erase from 0xa8100000-0xa87e0000: ..............................................................................................................
... Program from 0x80040c00-0x80300c00 at 0xa8100000: ............................................
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> fconfig -l
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000001
/home/alfa/Atheros_Beta5.0/linuxsrc/src/redboot_fon1/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7
.. exec
Boot script timeout (1000ms resolution): 2
Use BOOTP for network configuration: false
Gateway IP address: 0.0.0.0
Local IP address: 192.168.1.1
Local IP address mask: 0.0.0.0
Default server IP address: 192.168.1.254
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false