[ Aleph One home page | Company Information | Security Privacy and Terms of sale | Search ]
|
| LART Resources |
Here are files that have been tested and distributed on Aleph One LART development kits. If you mess things up these provide several 'known working' sets of matching blob, kernel, and ramdisk.
The ramdisk includes /etc/rc.d/rc.network and /etc/rc.d/rc.hd scripts to start up the networking and hd stuff respectively. hd dev nodes are included as are a useful set of modules for use with the KSB devices. The Ethernet driver is loaded on startup and if OK the network is configured - you may need to change the script to suit your own network config. The RAMDisk will need to be uuencoded before uploading.
Both kernel and ramdisk use the recent ttySAn serial/console interfaces instead of the older ttySn (which are actually PC-style serial ports). Note that this blob (from the 1.0.9_hack branch of CVS is actually more recent than, and superceedes, the 2.0.2 version that was mentioned on this page. The above ramdisk will need to be uucoded before uploading.
Thanx to Erik Mouw for this kernel/ramdisk pair. I found that the 2.4.0-test8-rmk5 kernel on the LART site doesn't boot. The glibc-2.1.2 one from the LART site won't execute any commands with the above kernel.
Note that the first few Aleph One boards were supplied with blob 1.0.8-pre2 installed, which didn't actually work. Users in this situation will need to install a different version to get anywhere. We currently recommend v2.0.4. Use uucoded version of above kernel (685K)
If you have one of the ethernet cards you need to know a few things to get it working. You need a kernel with ethernet support compiled in (CONFIG_EHTERNET=y and CONFIG_CS89x0=m). Use the current kernel, and RAMdisk. The RAMdisk includes matching modules and net and hd startup stripts. Even when the ethernet card is present the cs89x0 module gives confusing error messages suggesting that it has failed which actually refer to dev eth1. Unfortunately a bug in the driver means that if you disable the probe for eth1 then the driver doesn't work and claims that the RJ45 cable can't be detected, so you just have to put up with them for now. The driver does initialise the PCMCIA space itslef now so the ide driver is not needed, unlike previous releases. The current driver source is here - just replace the one supplied with your kernel source (until there is a proper rewrite of this driver - expected for kernel 2.5).
If you want to change the CPLD logic then you need the design files and Lattice Semiconductor's tools. Here is a tarball of the current files used on Aleph One boards. See the enclosed README.txt for details of what's what. It contains the base schematic files from which everything is derived, some 'project' files to make it easy to get started (beware they include absolute paths so you need to install to c:\armlinux\lart\ksb\ to use them 'as is'), and the resulting .jed files to program into the CPLDs. Two flavours are included for both early KSBs with two lsiVE2064's, and the later ones fitted with an lsiVE2128 as u9.
If you are uploading kernels and RAMdisks to your LART often you will soon get bored of changing serial speeds and typing commands. This script will do all this boring work for you. It will also flash the uploaded kernel and ramdisk for you.
The latest version of blob can now be obtained from blob.sourceforge.net. Blob 2.0.4 is the current release. This is recommended for all uses - it can programming a kernel and ramdisk (and itself) into LART flash and can pass kernel command-line parameters to kernels later than.
Last Updated: 2002.04.12
[ Aleph One home page | Company Information | Security Privacy and Terms of sale | Search ]