I've always been too curious...
To make a long story short I download the fonera source and built it. I run "make" save the configuration without altering anything in order to write the "Config.in" and then I run "make world". Correct, right?
Once it was built I compared the result of output (openwrt-ar531x-2.4-vmlinux.lzma) with the mtd4 of my Fonera. Interesting enough the kernel images are a bit different. From ver 7.0 r1 to ver .71.r1 the kernel has not changed for what I know. This can mean that FON didn't really release the last firmware source:-/ Or maybe I didn't build it how I was suppose to Another stange thing is that mtd_20050122.orig.tar.gz in the fonera source is not used to patch the kernel.
Anyway. I patched the kernel. Now all the MTD partions should be writeable. Please note that they were not writeable for a reason. Writing "Redboot config" is probably going to reset the FIS directory because it is on the same "erase sector". This is not a major problem since with Redboot we can easily recreate them and to install Openwrt we must do this anyway.
Ok... this is what is necessary to do starting with a Fonera with firmware FON 7.x already hacked (SSH access):
1 - Download the file http://rapidshare.com/files/9240866/openwrt-ar531x-2.4-vmlinux-CAMICIA.lzma.html on your on PC e move it on your Fonera /tmp folder
2 - Run "mtd -e vmlinux.bin.l7 write openwrt-ar531x-2.4-vmlinux-CAMICIA.lzma vmlinux.bin.l7"
3 - Restart the router. If everything went OK, it should work as usual. If you have the serial console you will see the messages of my hack
4 - Connect with SSH e move the Heini66 file ( http://rapidshare.com/files/9116527/out.hex.html ) on your /tmp
5 - Run: mtd -e "RedBoot config" write out.hex "RedBoot config"
6 - Reboot.
Your Fonera's Redboot should be now accessible at 192.168.1.254 through telnet.
NOTE: The procedure is UNTESTED yet. It's necessary that someone with a serial console tests it.
Heini66: thanks for your patience. Can you try this and let me know if it works?
Connecting to 192.168.0.5[192.168.0.5]:80
out.hex 100% |*****************************| 4096 00:00 ETA
root@(none):~# mtd -e "RedBoot config" write out.hex "RedBoot config"
Unlocking RedBoot config ...
Erasing RedBoot config ...
Writing from out.hex to RedBoot config ... [w]
The system is going down NOW !!
Sending SIGTERM to all processes.
Please stand by while rebooting the system.
+PHY ID is 0022:5521
Ethernet eth0: MAC address 00:18:84:13:57:08
IP: 192.168.1.254/255.255.255.0, Gateway: 0.0.0.0
Default server: 0.0.0.0
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version v1.3.0 - built 16:57:58, Aug 7 2006
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
RAM: 0x80000000-0x81000000, [0x80040450-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87f0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 10.000 seconds - enter ^C to abort
Run script at boot: true
.. fis load -l vmlinux.bin.l7
Enter script, terminate with empty line
Boot script timeout (1000ms resolution): 10
Use BOOTP for network configuration: false
Gateway IP address:
Local IP address: 192.168.1.254
Local IP address mask: 255.255.255.0
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
if you have only writen the camica-kernel, the reset of fonera should work. (90-120sec until lan led starts to blink...)
when openwrt installed, this button isn't used anymore. _________________ freenode.net #openwrt