|
The following are links to a complete source distribution package for uClinux.
This is a full source package,
containing kernel,
libraries and application code.
The following link is the latest snapshot source package that
includes support for a wide variety of CPU architectures.
It contains support for M68k, ColdFire, ARM, Sparc,
NEC v850, H8/300, Altera NIOS, Xilinx Microblaze
based target hardware and more.
It also contains 2.0.39, 2.4.32 and 2.6.19 kernel sources for uClinux,
and both the older uC-libc and newer uClibc-0.9.27 libraries.
You can find the latest experimental updates to the dist as patches in this
directory.
These patches are against the above full disrtibution,
so you only need apply one (typically the most recent).
A testing release leading up to the next full release is also available
now,
uClinux-dist-test-20070823.tar.bz2
or in gzip format
uClinux-dist-test-20070823.tar.gz.
Please report any problems to the uClinux-dev mailing list.
Here are links to older releases if you are looking for those:
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.
Instructions for compiling:
- Install a tool chain.
If you are using a binary tool chain package then install that now.
If you are building your own tool chain, then do that now.
- Un-archive the source package. It is a gziped tar image, so do:
tar xvzf uClinux-dist-XXXXXXXX.tar.gz
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 :-)
- Cd into the source tree:
cd uClinux-dist
- 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.
- Build the dependencies (this step is not required if you choose
to use the 2.6.x kernel):
make dep
- Build the image:
make
Thats it!
The exact binary files produced depends on your target.
The binaries files generated will be in the images directory.
Instructions for running
This is totally dependant on your target board.
They are all different.
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.
|
![[uCPenguin]](/images/logo.gif){kind=logo}
![[uClinux]](/images/ucllogo.gif)