5.1
Das U-Boot
10
Base/diffutils
Devel/binutils
Devel/gcc
Devel/make
Devel/patchutils
Utils/bzip2
Web/wget
The second requirement for building is the X-Scale cross-compiler itself.
The
GNUARM
project provides a wealth of information needed to build a
cross-compiler for ARM processors. Thankfully, it also provides an
installer
.
As of this writing, Boundary Devices currently uses the GCC-3.4.3 package
for
Cygwin
.
5.1.3
General build steps
Quick start:
wget http://easynews.dl.sourceforge.net/sourceforge/u-boot/u-boot-1.1.2.tar.bz2
bzcat u-boot-1.1.2.tar.bz2 | tar -xvf -
wget http://boundarydevices.com/u-boot-2005-10-21.patch.gz
gunzip u-boot-2005-10-21.patch.gz
patch -p0 <u-boot-2005-10-21.patch
cd u-boot-1.1.2
CROSS_COMPILE=arm-elf- make neon_config
-------- U-Boot Boundary Devices Specific Configuration Script --------
Choose display type (DA640X240 DA320X240 DA800X480 DA640X480 DA240X320 DA1024X768) []: DA1024X768
answer
Choose hardware type (NEONB NEON BD2003) [NEON]:
answer
Choose software type (WINCE LINUX) []: WINCE
answer
Include minidebug (y n) []: y
answer
CPU speed (100 200 300 400) []: 400
answer
Configuration successful.
make
Explanation.
The first four lines retrieve and extract the
Das U-Boot
sources and add
support for the Neon
R
and BD-2003 devices.
The last two lines configure for the Neon
R
board itself, and finally, build
a U-Boot binary. The prompts allow you to select the compile-time defaults
for the display, operating system, and CPU speed. Including minidebug
in your U-Boot image allows you to access the debugger while developing
U-Boot scripts.
When complete, you’ll find a file named
u-boot.bin
in your u-boot-1.1.2
directory.
5.1.4
Tailoring U-Boot for your application
The Boundary Devices patches (uboot neon bd2003.diff) make a variety of
decisions about the boot process which may not match with the needs of
December 28, 2005
Revision 2.8
