Flash Fonera2100 - problem

[pathlost]

Well... I have some good news!
I let the router in the cold, unpowered some hours. After I turned it on, I imediatly issued a "fis init -f" command! I lost connectivity, but after some minutes (I was way, but it was less than 45 mins) I have now some good areas on flash:

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> fconfig -l
Run script at boot: false
Use BOOTP for network configuration: true
Default server IP address: 0.0.0.0
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false

This partial sucess leads me to think of some hardware/ temperature problems... maybe I can cool the device and still use it.
But as you can see, I still have the boot script with default values.

I would like to load and store gargoyle by hand, without FonFlash. Can someone tell me if this is correct (taken from Open WRT):




loading file:
load -r -b 0x80100000 -m tftp [file_1] (here I put root.squashfs)

creating flash partition (this may take some time)
fis create -f 0xa8030000 -l 0x006c0000 -e 0x00000000 rootfs

loading file:
load -r -b 0x80100000 -m tftp [file_2] (here I put vmlinux.lzma)

creating flash partition (this may take some time)
fis create -f 0xa86f0000 -l 0x000e0000 -e 0x80041000 -r 0x80041000 vmlinux.bin.l7

Setting boot_script_data...
fis load -l vmlinux.bin.l7
exec


I have some doubts about the memory location...
And also if the loaded image will or will not change the Redboot boot script automatically.

[pathlost]

Hardware inspection:

LDO 3.3V damaged! output is @ 4V.
This is the rail that powers the flash. 4V is the absolute max for the flash, maybe this is the cause for errors.

I orderded a new LDO 3.3V, DPAK, to replace. I will post results.

[pathlost]

Issue is resolved.

The internal voltage regulator was damaged, providing 4V to the memory chip instead of 3.3V.

Replaced the regulator and proceeded with standard redboot method and all is ok. Now, flashing with gargoyle! Which is the version you would recommend?

[Lantis]

That's cool. Glad you got it sorted. I wouldn't have thought to check the Vreg.

[ispyisail]

Which is the version you would recommend?

A really old one

1.4.7
1.5.6
??
up to you

[pathlost]

version 1.4.7 is working nicely in client mode so far
DHCP disabled, repeater mode disabled. Connected ok to my main "G" 54 mbps wireless network.