The target systems are right now Atheros AP48/51/61 (eg Fon Fonera, UBNT NS/PS. Dlink DIR300 rev.A, Senao EOC-2610), AR5312/5/6/7/8 and AR7100 (in progress). Support for more reference designs to come.
The benefits of Micro Redboot are its small size (Its about half the size of a standard Redboot for these targets), a built in TFTP-Server (like in UBNT devices) for easy flashing with dd-wrt webflash images and a very fast boot in about 5 to 6 sec.. Micro Redboot supports many varys of HW combinations so that its very likly that your Platform is supported.
- *.rom = redboot for installing into flash
- *.elf = *.ram = redboot for executing out of ram
The following HW is supported at the time of writing
- kendin (realtek phy)
The first time Micro Redboot is installed and not configured or if you use Micro Redboot.ram and can reach the Redboot directly on 192.168.1.1: 9000 cause it doesnt try to boot and will be in waiting state.
Redboot already installed and configured
Many settings in Micro Redboot are hardcoded to prevent changes by mistake.
Press the reset button for 1 sec at powercyle to enable redboot access. You can access it with Telnet at 192.168.1.1 port 9000 for the time set in "Boot script timeout".
If you press the reset button for >= 5 sec the device will be reseted to defaults (reset nvram) as known.
And if pressed for more than 10 sec redboot and the tftp server for recovery will be enabled at 192.168.1.1. Use Tftp_flash for flashing.