Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Are there any guides for implementing firmware update on ARM?
I'm trying to setup a headless linux system on one of those small ARM boards that have flooded the market recently. The board has NAND flash on it and is capable of booting from it directly. The board also has a removable HDD attached to it, and the linux (debian wheezy ARM) is going to be installed on the NAND.
What's the recommended setup for a system that supports a firmware upgrade?
Personally I had an idea to split the NAND into multiple partitions. The first partition will be the /boot partiton with kernel images. The second one is going to contain the root filesystem, the third will hold program settings (I wanted to mount the /etc folder on it), and the last one is going to contain a maintenance firmware.
The device automatically boots and uses the main root partition for normal operation. At first I wanted to perform a firmware upgrade from the root partition itself, but I figured it's not a good idea to overwrite the root partition while the system is using it. This is why I added a secondary maintenance OS.
The next question is how to make the device boot the maintenance OS. We could have the main OS modify the boot settings, so that the next time device boots it will bring up the special OS. The downside is that if the main OS becomes corrupted somehow, we'd have no way to signal the device to boot the maintenance OS. The device could also boot onto this special OS by having a user hold down a button (GPIO signal high/low) on early boot.
This OS would display a web interface where the user can upload new firmware, and overwrite the main partition with it. Then reboot. Since this maintenance image cannot be overwritten it's a fool-proof method to do firmware upgrades.
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
Posts: 3,233
Rep:
hmm, my suggestion would be to look at an open source firmware based embeded system such as openwrt which does exaclty that, and figure out how they do it. usually embeded firmwares are uploaded via tftp or a web interface via an embeded web server, and then applied by a routine within the system, i've never implimented a sysem like this myself so i can't give you more details, but i hope i have at least pointed you in the right direction.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.