This is an old revision of the document!
Table of Contents
Introduction
Well this is the development branch, it is not for production use yet because of the wifi driver needs optimization (er fixing) for our embedded platform. It runs the CPU very hot and suffers from bad performance.
OpenWRT Development Branch (trunk, r23446, kernel 2.6.36)
When preinit starts, SES light turns green. If you are holding the SES button, or at least press it quickly as soon as light turns green, then failsafe should start. Failsafe is indicated by orange light. Then you may telnet to 192.168.1.1 with a PC connected to a LAN port. You may want to do this the first boot anyway, to run “firstboot” to format jffs partition, tho it should work outside of failsafe.
- the bootlog: http://wrt.scottn.us/openwrt-trunk-bootlog.txt
upgrade from backfire
Since I never edited sysupgrade correctly in old version, I did this craziness to upgrade from the backfire build to this development build:
root@OpenWrt:~# source /lib/upgrade/common.sh root@OpenWrt:~# run_ramfs mount: mounting mini_fo:/overlay on /mnt failed: Function not implemented Please press Enter to activate this console. BusyBox v1.15.3 (2010-09-14 10:19:20 EDT) built-in shell (ash) Enter 'help' for a list of built-in commands. / # cd /tmp /tmp # wget http://wrt.scottn.us/wrtu54g-tm-openwrt-devel.bin Connecting to wrt.scottn.us (208.77.101.28:80) wrtu54g-tm-openwrt-d 100% |*******************************| 2250k 00:00:00 ETA /tmp # mtd erase linux Unlocking linux ... Erasing linux ... /tmp # mtd erase rootfs Unlocking rootfs ... Erasing rootfs ... /tmp # mtd erase rootfs_data Unlocking rootfs_data ... Erasing rootfs_data ... /tmp # mtd write wrtu54g-tm-openwrt-devel.bin linux:rootfs:rootfs_data Unlocking linux ... Unlocking rootfs ... Unlocking rootfs_data ... Writing from wrtu54g-tm-openwrt-devel.bin to linux ... Writing from wrtu54g-tm-openwrt-devel.bin to rootfs ... Writing from wrtu54g-tm-openwrt-devel.bin to rootfs_data ... /tmp # reboot