Difference between revisions of "Compiling the iMote2 kernel"
From University of Washington - Ubicomp Research Page
m |
m |
||
| Line 83: | Line 83: | ||
<bash>${IMAGE}:: force | <bash>${IMAGE}:: force | ||
@scripts/platx_config</bash> | @scripts/platx_config</bash> | ||
| + | Now you're ready to build the kernel: | ||
<bash>mkdir ../kernel | <bash>mkdir ../kernel | ||
| Line 96: | Line 97: | ||
=== Flashing the kernel === | === Flashing the kernel === | ||
| + | <ul> | ||
You will need to specify the platform (SG2/Intel Mote2) and JTAG cable that you are using (Intel(R) JTAG Cable/JTAG CPU) to XFlash. The following assumes you are programming an Intel Mote2 with a Macraigor Raven JTAG: | You will need to specify the platform (SG2/Intel Mote2) and JTAG cable that you are using (Intel(R) JTAG Cable/JTAG CPU) to XFlash. The following assumes you are programming an Intel Mote2 with a Macraigor Raven JTAG: | ||
| Line 110: | Line 112: | ||
xflash -p intelmote2 -tt "Intel(R) JTAG Cable" fs.jffs2 -offset 0x00240000 | xflash -p intelmote2 -tt "Intel(R) JTAG Cable" fs.jffs2 -offset 0x00240000 | ||
</pre></code> | </pre></code> | ||
| + | </ul> | ||
Revision as of 01:25, 9 November 2006
Contents
Downloads
- PlatformX 1.0 Release from sourceforge.net
- MSB2 Patches from msp/system/kernel available here
- iMote2 Toolchain (either the normal handheld.org toolchain or perferably the Mainstone version with an updated version of binutils
- the 2.6.14 linux kernel available from kernel.org
Steps
Extracting all the Images
-
Assuming you placed the platformX release, patches, and kernel in the same directory you could extract them all using the following commands:
<bash>tar zxf linux-2.6.14.tar.gz
tar zxf SG2Release-1_0.tgz
tar zxf msb2_patches.tgz</bash>
Patch the kernel
-
First we apply the SG2 release patches then we apply our MSB2 patches:
<bash>cd linux-2.6.14
echo "Applying SG2 Patches"
patch -p1 < ../SG2Release-1_0/src/patch-2.6.14-sg2-10
echo "Applying MSB2 Patches"
patch -p1 < ../msp-linux-2.6.14-pxa-mmc.patch
patch -p1 < ../msp-linux-2.6.14-uart.patch
patch -p1 < ../msp-linux-2.6.14-sd-detect.patch</bash>
Configure the kernel
-
At this point you can either use the normal SG2 configuration or apply the msb2 standard configuration. Be sure to add your toolchain to your path, if you've installed it in /usr/local/arm/3.4.3_binutils you could do something like this:
<bash>export PATH=/usr/local/arm/3.4.3_binutils/bin/:$PATH
export ARCH=arm
export CROSS_COMPILE=arm-linux-</bash>
- Device Drivers
- USB Support
- USB GadgetSupport
- Support for USB Gadgets (compile into the kernel)
- USB Gadget Drivers (compile into the kernel)
- Make sure 'Ethernet Gadget (with CDC Ethernet Support)' is selected
- Select 'RNDIS support (EXPERIMENTAL)'
- USB GadgetSupport
- USB Support
- export ARCH=arm
- export CROSS_COMPILE=/usr/local/arm/3.4.1/bin/arm-linux-
- export PATH:=${PATH}:/usr/local/arm/3.4.1/bin/
SG2 Configuration
-
<bash>export ARCH=arm
export CROSS_COMPILE=arm-linux-
make stargate2_defconfig
make oldconfig</bash>
MSB2 Configuration
-
<bash>export ARCH=arm
export CROSS_COMPILE=arm-linux-
cp ../msp-linux-2.6.14-config ./.config
make oldconfig</bash>
RNDIS (Windows XP) Ethernet Gadget Configuration
-
If you'd like to be able to connect the iMote2 to a Windows XP host instead of a linux host you can use the RNDIS patch to add Windows XP support to the kernel. Download the patch from here to your build directory. Note, that this patch currently compiles support into the kernel and not as a module.
<bash>export ARCH=arm
export CROSS_COMPILE=arm-linux-
cp ../msp-linux-2.6.14-config ./.config
patch -p1 < ../msp-linux-2.6.14-winXP-rndis.patch
make oldconfig</bash>
Next you will need to do a make menuconfig (after setting up the ARCH/CROSS_COMPILE/path) and select:
Compile the kernel
You can then build the kernel as you normally would or perform any additional steps you want to before building. Note that if you are using the Mainstone tools instead of a 3.4.1 toolchain installed in /usr/local/arm/3.4.1 you will need to edit Makefile.platx and comment out the export lines at the top. <bash>...
... </bash> You can also remove the platx_config to get rid of an annoying error message in the SG2_1.0 release: <bash>${IMAGE}:: force
@scripts/platx_config</bash>
Now you're ready to build the kernel:
<bash>mkdir ../kernel make zImage make modules make modules_install cp arch/arm/boot/zImage ../kernel/ cp -a modules/lib/modules/2.6.14_r1.0/ ../kernel/ </bash> Note you should remove the '../kernel' directory each time you do this to avoid getting a stale copy; however, I'm not about to place rm -rf commands in things people will paste arbitrarily
Flashing the kernel
-
You will need to specify the platform (SG2/Intel Mote2) and JTAG cable that you are using (Intel(R) JTAG Cable/JTAG CPU) to XFlash. The following assumes you are programming an Intel Mote2 with a Macraigor Raven JTAG:
xflash -p intelmote2 -tt "JTAG CPU" blob -offset 0x00000000
xflash -p intelmote2 -tt "JTAG CPU" zImage -offset 0x00040000
xflash -p intelmote2 -tt "JTAG CPU" fs.jffs2 -offset 0x00240000
And the following assumes you are programming an Intel Mote2 with an Intel JTAG
xflash -p intelmote2 -tt "Intel(R) JTAG Cable" blob -offset 0x00000000
xflash -p intelmote2 -tt "Intel(R) JTAG Cable" zImage -offset 0x00040000
xflash -p intelmote2 -tt "Intel(R) JTAG Cable" fs.jffs2 -offset 0x00240000
