Well, if you want, you can also expand it to make it simply conditional:


This way, you have a variable to select what you want to boot. Boots from mmc if kernel is set to 1, otherwise from NAND. It should post a message on serial if neither of them worked. Note that it will try the other boot if the other one failed. You're setting a preference with the kernel value.

I hope I got it correct; I quickly adapted my embedded boot logic to your examples. The or in the bootcmd is typically disaster recover; I go about erasing the u-boot variables and reset (was previously mentioned). In that case, it will default back to the hardcoded values.

In our development environment, this is further expanded with a NFS version that will fetch the kernel over TFTP with DHCP (DHCP filename entry) , boot the kernel and then mount a NFS system with that particular version (kernel value 0).

This way, you can maintain lots of development systems with several NFS filesystems and kernel files without much customisation of the U-Boot variables and offloading the customisation to a central DHCP server config file.

Got a note that my Sheevas got shipped beginning of this week, so I'll be trying this out next week or so; need to port it fully. If there is interest, I could add more info about that later on.

I'ts a copy paste from a link where I wrote down a setup for KNX/EIB, so ignore the non relevant bits.


Trouble Shooting

You do not need JTAG to reflash your SheevaPlug, go to the section Flashing the system from the bootloader if you just want to have a cleanly flashed system.. the following paragraphs should only be used when your sheeva got bricked for some reason.
Clearing and re-writing the system on the Sheeva

The creation of these files (UbiFS, the kernel and bootloader) is readily described on the net, PlugComputer is a good place to start. For convenience, the files are bundled in one archive. Install openocd on your your system, download the sheevaplug-installer-v1.0.tar.gz file from openplug.org and extract it.


If OpenOCD complains with a similar message:

you might need to change the file: sheevaplug-installer-v1.0/uboot/openocd/config/interface/sheevaplug.cfg


This is due to a changed vendor ID after 07/2009.

Connect with a telnet session to your OpenOCD session.

You don't really need retail customers to have this. You just need cluelessness; any (corporate) level will do (be it end users, or managers). 

From what you describe, your bootloader is stuck in the mmc commands and never gets further due to this. I would need to test this, but unfortuntately; I'm waiting for more than 4 weeks for my next plugs to do more experimenting on.

However, I would expect you'll need to use an or operator, this is e.g. the default boot command I'm using for an PowerPC based CPU; where I clear the system if the system fails to boot with the bootloader settings:


So if runsystem (a script) blocks the system, I clear the flash. You'll probably need something along those lines for your MMC/NAND setup. It'd be interesting to test it; but you'll probably have to wait a couple of more weeks since I haven't received a shipment notice from GlobalScale yet.

• Added HOWTO on plugcomputer wiki
• Added http://chiana.homelinux.org/~marc/eib_sheeva.html extensive decription to clean up Sheeva Plug before using it
• Provided base Lenny system to use with 2.6.31.5

The previous two points are merely a collection of other available work; hopefully in an easy to use fashion.

linknx 0.0.1.26-5 and eibd-server 0.0.4-4:

- fixed initscripts (update-rc.d was not running)
- fixed dependencies between scripts
- more testing on /var/log/knx and /var/run/knx

Packages are available for Lenny and later on armel and amd64, if someone is interested for other arch, I'll add them to the repos.

Looks interesting to integrate it with my KNX/EIB Home Automation Centre HOWTO :-) The combination of these two devices beats commercial products in price and in functionality :-)

Nice.

- added support for mysql
- some patch backports

In order to use knxweb; install the following from a normal Debian repos



The repos is in my case:


enable fastcgi


Install the backend packages:


modify /etc/default/eibd-server and /etc/default/linknx to enable the daemons and to connect to your interface of choice and restart the daemons.


You should have a basic system. Note that it will only be useful if you modify the /etc/linknx/house.xml configuration to match your addresses and rules.

In order to get the webinterface, download knxweb from sf.net and extract in /var/www/. You will then need to modify the background images and design your layout with the built-in editor (the images will need to be overwritten on your plug, there is no editor support for that as of yet).

Since knxweb generates a lot of http accesses, you might want to disable in /etc/lighttpd/lighttpd.conf the access logging module (mod_accesslog).

Sweet Home 3D (www.sweethome3d.eu/download.js) is a nice cross platform and easy to use 3D modeling tool I used for the att.d screenshot.

I added a repository that contains the relevant debian packages:

A more in detail description/HOWTO of the setup and configuration  can be found on
http://chiana.homelinux.org/~marc/eib_sheeva.html

Even though there is little 'porting' to do due to the excellent quality of the upstream projects; I've been using

• eibd-server: http://www.auto.tuwien.ac.at/~mkoegler/index.php/eibd
• linknx: http://linknx.sourceforge.net/
• webknx: http://knxweb.sourceforge.net/

to automate tasks like controlling heating, lighting and closing/opening shutters from a SheevaPlug (used to be a NSLU2). I am currently working on getting the packages in Debian. The tools work with EIB (European Installation Bus) aka KNX.

The interfacing towards the bus is done by eibd-server and linknx is a small daemon that keeps track of simple tasks and states. knxweb provides a AJAX interface on your installation that shows the current state of the system (lights on/off, shutters, heating, temperature, ...). The linknx configuration is done with a XML representation and tasks can be specified (amongst others) on a time base; or even at sunrise/sunset; calculated based on your coordiates.

Installling the packages on a system that ships is peanuts.