Is my Fonera 2201 bricked ?

[Baron3K]

Hi all, while trying to update my fonera manually something went wrong. I'am unable now to unbrick my device. I connected a serial console and this is what i get.

No board config data found!
+Couldn't find valid MAC address for enet0. Using default!
... waiting for BOOTP information ----> after pressing CTRL+C

Ethernet eth0: MAC address 00:03:7f:e0:02:bf
Can't get BOOTP info for device!

RedBoot(tm) bootstrap and debug environment [ROMRAM]
OpenWrt certified release, version 1.1 - built 22:32:28, May 7 2007

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: FON 2201
RAM: 0x80000000-0x81000000, [0x80040290-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87f0000, 128 blocks of 0x00010000 bytes each.
RedBoot>

I'AM UNABLE TO RUN FIS INIT & FIS INIT -F PROCEDURE


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: V
Error writing FIS directory at 0xa87e0000: Unknown error
RedBoot> ---- looks like problems saving into that memory allocation.


PARTITION LIST LOOKS LIKE THAT

RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xA8000000 0xA8000000 0x00030000 0x00000000
FIS directory 0xA87E0000 0xA87E0000 0x0000F000 0x00000000
RedBoot config 0xA87EF000 0xA87EF000 0x00001000 0x00000000
RedBoot>

NOTHING THERE

RedBoot> bdrestore
Board config found at 0xa8790000
No board config data found!
RedBoot>

I can set IP - load firmware by TFTP, flash the rootfs, but it seems like there is a problem with writing to the allocation.

Program from 0x80ff0000-0x81000000 at 0xa87e0000

besides that board config is missing. Can I somehow get a spare one for fon 2201 ?

[DoesItMatter]

I actually have had the same problem on my Fon 2201+

I get that memory error when doing "fis init -f"

at the exact same spot too.

I believe its the flash chips are weak/cheap and don't have a
great lifespan. i.e. that '50,000' write cycles, isn't really 50,000 writes.

I've done a couple years of flashing with both DD-WRT and Gargoyle.
I'm not that disappointed as its always been a test router.

You can still flash Gargoyle, as its size is below the error point.

I'm currently running 1.0.16 just fine on it, even with the error.

re-do a Fon Flash and try loading 1.0.16, and see if that works.

If it does, then Fon Flash 1.1.8 or 1.2.2 and see if it works.

They do get bigger with higher versions, so you may run into a
firmware that doesn't work and hits the bad spot of flash.

Be aware, it will eventually die. I think it might be possible to
re-solder on a new flash chip, but no idea.

I know I got my use/testing out of mine, so I won't be that sad.

----------------------

Baron3K - are you located in the USA?