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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am trying to determine the best way to upgrade software on my target. For development we can a use the command line shell of our bootloader program, but we need the unit to auto-update in the production version. Currently, we TFTP the 2 files (kernel
and filesystem) to ram, and then copy the ram files to the MTDs in flash. A reboot then brings us up on the new filesystem.
Apparently, the kernel and filesystem is expanded on-the-fly as needed by program operations into ram. So this is where I (think) I am running into a problem. Sometimes during the erase and programming of the MTDs, the target locks up; sometimes I get no warnings, sometimes I get
"Error -3 while decompressing!
To minimize the risk of loading code from the filesystem, I kill off the majority of the processes, although I am sure there are more I can kill. I don't think this is the answer to my problem.
I am developing with a MIPS processor with MMU, Linux 2.6.10 kernel, compiled with UClibc, and BusyBox v1.2.2.
My kernel is in mtd0, and mtd1 contains the filesystem, as CRAMFS.
1.) What is the "right" way to update my file system and kernel?
2.) Can I use switch_root or pivot_root to help this situation?
I'd divide it into two phases:
1. Downloading - getting the files and checking if they're correct (any variant of SHA or MD5, for instance). No upgrade phase it the above fails, for obvious reasons.
2. Upgrading - remove all not needed processes and the upgrade. If possible, switch to a special mode with no external applications, only the task to upgrade. Or use priorities to give the upgrade process the highest one and full access to the MTDs.