Uclinux - Embedded Linux - Microcontroller Project - Source Distribution
Uclinux - Embedded Linux - Microcontroller Project - Source Distribution
org/pub/uClinux/dist/
Home
The following are links to a complete source distribution package for uClinux. This is a full source package,
What is uClinux? containing kernel, libraries and application code.
Status The following link is the latest snapshot source package that includes support for a wide variety of CPU
architectures. And it includes pre-canned configurations for hundreds of boards from dozens of different
Getting started with uClinux vendors. (Note that this code base is designed to run on both non-MMU processors and processors with
MMU hardware). It also contains 2.0.39, 2.4.34 and 2.6.36 kernel sources for uClinux, and both the older
FAQ
uC-libc and newer uClibc-0.9.29 libraries.
uClinux Ports
Full Source Distribution (20101026) (gzip archive) (md5 sums)
The Developers
E-Mail Forum These images are mirrored at sourceforge.net/projects/uclinux/files/, and I would recommend you download
them from there. It will be much quicker! Here is a direct link to the bziped source package.
Contact us
HTTP download
Full Source Distribution (20101026)
Sponsor Links
You can find the latest experimental updates to the dist as patches in this directory. These patches are
against the previous full distribution, so you only need apply one (typically the most recent). As a new stable
full release is made the patches will from then forward be generated against that.
Here are links to older releases if you are looking for those:
ColdFire Links:
uClinux-dist-20100825.tar.bz2
HOME uClinux-dist-20100628.tar.bz2
uClinux-dist-20100315.tar.bz2
FAQ uClinux-dist-20090618.tar.bz2
uClinux-dist-20080808.tar.bz2
DEVELOPMENT NOTES uClinux-dist-20070130.tar.gz
uClinux-dist-20060803.tar.gz
SCREEN SHOT
uClinux-dist-20051110.tar.gz
SOURCE uClinux-dist-20051014.tar.gz
uClinux-dist-20041215.tar.gz
BINARY uClinux-dist-20040408.tar.gz
uClinux-dist-20040218.tar.gz
BOOT LOADERS uClinux-dist-20030909.tar.gz
uClinux-dist-20030305.tar.gz
EMAIL - [email protected] uClinux-dist-20020927.tar.gz
uClinux-dist-20020701.tar.gz
uClinux-dist-20020502.tar.gz
uClinux-dist-20020220.tar.gz
These are source only packages. You will need a tool chain to generate anything usefull from this source. A
number of pre-built binary tools packages with instructions on installation are available at www.uclinux.org.
Links below for the most common ones:
If you wish to rebuild the tool set from scratch then follow the links to the above binary tool chains for
helpful build scripts. For many VM targets the toolchains are quite standard (usual binutils and gcc
packages). Tool chains for the non-MMU targets tend to be a little more tricky to build (needing binutils, gcc,
elf2flt at least). Again follow the links above for appropriate versions that are known to work.
Snapgear have a number of pre-compiled toolchains that can be used with the dist in their downloads area.
The CodeSourcery tool chains have also successfully been used with the uClinux-dist, find them at their site.
This will dump the source into a uClinux-dist directory. Typically you would do this somewhere in
your local user directory. (Good practice dictactes that you don't build things like this as root :-)
4. Configure the Linux kernel. Configure the build for your specific target. Do the following:
make xconfig
Or you can use the menuconfig or config make target if you are not running the X windows system on
your development machine.
The top level selection is strait forward if you know the vendor of the board you want to compile for.
You can choose also to modify the underlying default kernel and application configuration if you want.
At first I suggest using the default configuration for your vendors board. It will almost certainly work
as is on your board.
5. Build the dependencies (this step is not required if you choose to use the 2.6.x kernel):
make dep
Thats it!
The exact binary files produced depends on your target. The binaries files generated will be in the images
directory.
Check in the Documentation directory at the top level of the source tree for a HOWTO file for your specific
board. If present it will list exactly how to load and run images generated from this source.
Otherwise you will need to consult the documentation supplied with your board.
Notes
Console output is generally from the primary serial port. The baud rate is typically the default for that board.
You should see the Linux kernel startup messages come out. The shell is interactive, a small set of shell tools
is available and can be executed.
© Copyright 1999 - 2000 Moreton Bay © Copyright 1999 - 2000 Rt-Control Inc. © Copyright 2000 - 2001 Lineo © Copyright 2002 - 2008 SnapGear Inc