Difference between revisions of "EBC Exercise 08 Installing Development Tools"

From eLinux.org
Jump to: navigation, search
(Finding the Correct Kernel)
(download)
(27 intermediate revisions by 3 users not shown)
Line 10: Line 10:
 
'''Tip:''' Run this exercise using a wired connection if you can. The Ubuntu wireless driver can be finicky, and if it stops working you'll have to restart some of this.
 
'''Tip:''' Run this exercise using a wired connection if you can. The Ubuntu wireless driver can be finicky, and if it stops working you'll have to restart some of this.
  
== Install development environment ==
+
== The Kernel ==
  
The step is to get the crosscompilers, etc. installed. Generally you do this install on your local copy of Linux. Some of these installs can take a long time (one took me 12 hours, slow download times), so you may want to install on a remote server that's always connected to the internet. If so, see the tips [[ | below]]
+
These instructions have been tested for the 3.2.25 kernel.
  
=== Get the setup scripts ===
+
=== download ===
 +
These are notes are based on [https://github.com/beagleboard/kernel/blob/6682025752d0b807119c1e363a0b1b9bfe2ab453/README.md Beagleboard kernel git site].
  
First install <code>git</code> by running the following on your host computer.
+
First download the tools needed to compile the kernel. This took about 25 seconds.
 +
host$ '''sudo apt-get install -y git lzop gcc-arm-linux-gnueabi uboot-mkimage'''
  
  host$ '''sudo apt-get install git-core'''
+
Next download the tools to get the kernel and the patches needed to make it run on the beagle.  (2.5 seconds)
 +
host$ '''cd ~/BeagleBoard'''
 +
  host$ '''git clone git://github.com/beagleboard/kernel.git'''
 +
host$ '''cd kernel'''
 +
host$ '''git checkout 6a7c4284a16fed3dae87f4aef78b59c902e4da84 -b beaglebone-3.2'''
  
(Here is a nice [http://progit.org/book/ git tutorial]Take a look at it if you want to understand the commands that follow. We'll explore it in more depth in a later exercise.)
+
Next download the kernel and the patches.  Before running '''./patch/sh''', take a look at it.  Can you figure out what it's doing?  Also look at '''patch_script.sh''', it's where the details are. The downloading/patching process takes some 39 minutes.
 +
host$ '''less patch.sh patch_script.sh'''
 +
host$ '''./patch.sh'''
 +
host$ '''cp patches/beaglebone/defconfig kernel/arch/arm/configs/beaglebone_defconfig
 +
host$ '''wget http://arago-project.org/git/projects/?p=am33x-cm3.git\;a=blob_plain\;f=bin/am335x-pm-firmware.bin\;hb=HEAD -O kernel/firmware/am335x-pm-firmware.bin'''
 +
  host$ '''md5sum kernel/firmware/am335x-pm-firmware.bin'''
 +
17d6a4c24d3cb720aa9ed4522cb891fc  kernel/firmware/am335x-pm-firmware.bin
  
Then run the following to load the meta data.
+
=== compile ===
 +
Once patched you are ready to compile the kernel.  The first time takes a while.  Mine tool 4 minutes, but I was running on 8 cores.  Set the '''-j''X'' ''' to match the number of cores you have. '''uImage''' is the kernel!
 +
host$ '''cd kernel'''
 +
host$ '''make beaglebone_defconfig'''
  
I have everything in a <code>~/BeagleBoard</code>, so here is how I setup things:
+
Now that you know it's working, let's compile it. First set the paths to find the cross-compiles. Put the following in a file, call it ~/.oe/'''crossCompile.sh'''.
  
  host$ '''cd'''
+
  export ARCH=arm
  host$ '''mkdir -p BeagleBoard'''
+
  export CROSS_COMPILE=arm-linux-gnueabi-
host$ '''cd BeagleBoard'''
+
Do the above once
host$ '''git clone git://github.com/Angstrom-distribution/setup-scripts.git oe'''
+
host$ '''cd oe'''
+
  
(The git took 4.5 seconds.)
+
Now ''source'' the file.
This creates a directory for open embedded (<code>oe</code>) and gets the script to download Ångström. What files do you see?
+
host$ '''source ~/.oe/crossCompileEnv.sh'''
 +
Do the above once per terminal session.
  
=== Setting up for the BeagleBoard ===
+
host$ '''make -j9'''
 +
host$ '''make uImage'''
 +
Do the above every time you recompile the kernel
  
Now let's setup <code>local.conf</code> for our needs:
+
You also need all the kernel modules. Here we create a directory to install them in. (a few seconds)
  $ gedit conf/local.conf
+
  host$ '''mkdir ../rootfs'''
Add the following to the '''end''' of the file.
+
  host$ '''make INSTALL_MOD_PATH=../rootfs modules_install'''
  MACHINE ?= "beagleboard"
+
Look at this block of lines:
+
<pre>
+
# Make use of SMP and fast disks
+
PARALLEL_MAKE = "-j2"
+
BB_NUMBER_THREADS = "2"
+
</pre>
+
Here you can tell it how many parallel threads to run. If you have several cores on your machine, make this number big. If you have only one core, you might be better performance setting it to 1. If you have no clue which value to pick, Gentoo users suggest 1 more than the number of cores in your computer. More details are [http://wiki.openembedded.org/index.php/Advanced_configuration here].
+
* PARALLEL_MAKE sets the number "gcc" threads (same as make -j4 at compile time
+
* BB_NUMBER_THREADS sets the number of bitbake threads, (one thread can be downloading, while another compiles)
+
  
To save you a lot of time, it is useful to disable locale generation for all but the one you needAdd this to local.conf
+
=== install ===
  GLIBC_GENERATE_LOCALES = "en_US.UTF-8 en_GB.UTF-8 de_DE.UTF-8 fr_FR.UTF-8 pt_BR.UTF-8 es_ES.UTF-8 kn_IN.UTF-8 ml_IN.UTF-8 ta_IN.UTF-8"
+
Copy the kernel and the modules to the Beagle(a minute or so)
 +
  host$ '''cd ..'''
 +
host$ '''scp kernel/arch/arm/boot/uImage root@beagle:/boot/uImage-3.2.25+
 +
host$ '''cd rootfs'''
 +
host$ '''find -H -depth | cpio -o -H crc | ssh root@beagle 'cd /; cpio -id' '''
  
Now run:
+
Now log into the beagle and move some things around.
 +
host$ '''ssh root@beagle
  
  host$ '''./oebb.sh config beagleboard'''
+
This will copy the kernel to the ext4 partition.
 +
  beagle$ '''cd /boot'''
 +
beagle$ '''rm uImage'''
 +
beagle$ '''ln -s uImage-3.2.25+ uImage'''
  
I got some errors; some things are missing
+
This will copy to the FAT partition.
  host$ '''ls -ls /bin/sh'''
+
  beagle$ '''mkdir /media/mmcblk0p1'''
  0 lrwxrwxrwx 1 root root 4 Mar 29 14:53 /bin/sh -> dash
+
  beagle$ '''mount /dev/mmcblk0p1 /media/mmcblk0p1'''
host$ '''sudo rm /bin/sh'''
+
  beagle$ '''cp /boot/uImage-3.2.25+ /media/uImage'''
host$ '''sudo ln -s /bin/bash /bin/sh'''
+
  host$ '''ls -ls /bin/sh'''
+
0 lrwxrwxrwx 1 root root 9 Aug 30 10:38 /bin/sh -> /bin/bash
+
host$ '''sudo apt-get install gawk'''
+
  
Now try again
+
=== reboot ===
host$ '''./oebb.sh config beagleboard'''
+
Make sure screen is running on your host so you can see the shutdown and boot processes.
  host$ '''./oebb.sh update'''
+
  host$ '''screen /dev/ttyUSB1 115200'''
  
This will bring in all the tools you needThe config took about 3.5 minutes on my machine, update took about 1 minute.
+
If you get an error try changing making yourself the owner of /dev/ttyUSB1.
 +
  host$ '''sudo chown ''yoder:yoder'' /dev/ttyUSB1'''
 +
host$ '''screen /dev/ttyUSB1 115200'''
  
=== Build a small program ===
+
Then restart you beagle
 
+
  beagle$ '''shutdown -r now'''
Before the first time you run bitbake you need to do the following to set up the environmental variables:
+
  host$ '''source ~/.oe/environment-angstromv2012.05'''
+
 
+
Take a look in the file and see what it is doing.
+
host$ '''less ~/.oe/environment-angstromv2012.05'''
+
 
+
To see if everything is ready, run the following
+
 
+
host$ '''bitbake nano'''
+
 
+
nano is a small editor.  We really don't need nano, but if it can be compiled we know we have everything in place.  I get the following error when I run the bitbake:
+
<pre>
+
Pseudo is not present but is required, building this first before the main build
+
.
+
.
+
.
+
ERROR:  Poky's config sanity checker detected a potential misconfiguration.
+
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
+
    Following is the list of potential problems / advisories:
+
 
+
    Please install following missing utilities: diffstat,texi2html,makeinfo,cvs,svn,chrpath
+
 
+
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
+
</pre>
+
So, some programs are missing.  Install them with:
+
host$ '''sudo apt-get install diffstat texi2html texinfo subversion chrpath gettext'''
+
This took just a few minutes.
+
 
+
Now run:
+
host$ '''bitbake nano'''
+
This will take a while. Mine first said it has 77 tasks to do.  Once those were done it had 1113 tasks.
+
 
+
Below is a table of the times from last year.  Add your bitbake time to this year's table.
+
{| style="color:green; background-color:#ffffcc;" cellspacing="0" border="1" cellpadding="5"
+
|+ Initial <tt>bitbake nano</tt> Winter 2011-2012 runtimes
+
! Processor
+
! Settings
+
! Run Time
+
|-
+
| 8 Core virtual machine
+
| PARALLEL_MAKE = "-j8"<br>BB_NUMBER_THREADS = "8"<br>
+
| 2.5 hours
+
|-
+
| Intel Core 2 Duo T7800, 2.60 GHz
+
| PARALLEL_MAKE = "-j2"<br>BB_NUMBER_THREADS = "2"<br>
+
| 1:55
+
|-
+
| AMD Phenom(tm) II X3 720 Processor, 2.80 GHz
+
| PARALLEL_MAKE = "-j3"<br>BB_NUMBER_THREADS = "3"<br>
+
| 1:44
+
|}
+
{| border="1" cellspacing="0" cellpadding="5"
+
|+ Initial <tt>bitbake nano</tt> 2011 runtimes
+
! Processor
+
! Settings
+
! Run Time
+
|-
+
| Dell E521 with AMD Athlon 64 dual-core
+
| PARALLEL_MAKE = "-j4"<br>BB_NUMBER_THREADS = "4"<br>Psyco? Yes.
+
| 1.5 hours
+
|-
+
| Intel Core 2 Duo T7800, 2.60 GHz
+
| PARALLEL_MAKE = "-j1"<br>BB_NUMBER_THREADS = "1"<br>Psyco? No.
+
| 1:46
+
|-
+
| Intel Core 2 Duo T7800, 2.60 GHz
+
| PARALLEL_MAKE = "-j4"<br />BB_NUMBER_THREADS = "3"<br />Psyco? Yes.<br />Ubuntu 10.04 Running in VMWare Workstation 7.1.3 Under Windows 7 32-bit
+
| 1:42
+
|}
+
 
+
Once nano is done building you can find it with:
+
host$ '''find . -name nano'''
+
Can you figure out which one is the nano that will run on your Beagle?  I found it here:
+
 
+
build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nano-2.2.5-r2.0/package/usr/bin/nano
+
 
+
== Download and Compile the Kernel ==
+
 
+
The next step is to download and compile the kernel.
+
 
+
We want to keep the kernel source code around so we can experiment with it.  Do this:
+
host$ '''gedit conf/local.conf'''
+
Find the line near the '''top''' that says <code>INHERIT += " rm_work "</code> and comment it out.  This will save the source code.
+
# INHERIT += " rm_work
+
 
+
Exit gedit and do the following:
+
 
+
host$ '''source ~/.oe/environment-angstromv2012.05'''
+
host$ '''cd ~/BeagleBoard/oe'''
+
host$ '''bitbake virtual/kernel'''
+
 
+
Mine says it has 769 tasks to do.  It took about 1 hour to do them.  Once done you should get a kernel that will work.
+
 
+
If you accidentally run bitbake without commenting out the above line, after it runs you can comment out the INHERIT line and then run
+
 
+
host$ '''bitbake -c clean virtual/kernel'''
+
host$ '''bitbake -f -c compile virtual/kernel'''
+
 
+
This second run should take less time (one timing: first run took 3.5 hours; the recompiling took 25 minutes).
+
 
+
=== Finding the Correct Kernel ===
+
 
+
When you do the '''bitbake virtual/kernel''' you get the most recent kernel. How do you know which version you got?  Look in the source directory.
+
 
+
host$ '''cd ~/BeagleBoard/oe; ls -F'''
+
build/  conf/  oebb.sh*  pseudodone  scripts/  sources/
+
 
+
Take a look in the '''sources''' directory.
+
 
+
host:~/BeagleBoard/oe$ '''ls -F sources'''
+
bitbake/        meta-ettus/    meta-nslu2/        meta-ti/
+
downloads/      meta-handheld/  meta-openembedded/  meta-xilinx/
+
layers.txt      meta-intel/    meta-openpandora/  openembedded-core/
+
meta-angstrom/  meta-java/      meta-opie/
+
meta-browser/  meta-kde/      meta-raspberrypi/
+
meta-efikamx/  meta-mono/      meta-smartphone/
+
 
+
Here you see directories that contain information about various repositories that were used in pulling together all the sources used to build the kernel, u-boot, and the cross-compilers. Look around a bit an see what you can learn.
+
 
+
Let's see what was built when we made the kernel.
+
 
+
host:~/BeagleBoard/oe$ '''cd build; ls -F'''
+
sstate-cache/  tmp-angstrom_v2012_05-eglibc/
+
 
+
We are interested in the second directory. This is where the Angstrom build is kept, it's the 2012 version.  Open Embedded can support other distributions and the software is set up so you can work with more than one distribution as the time. We're only working with Angstrom though.
+
 
+
The '''-eglibc''' tells us what libraries were used in making the build. We'll talk about libraries later.  Look further:
+
 
+
host:~/BeagleBoard/oe/build$ '''cd tmp-angstrom_v2012_05-eglibc/; ls -F'''
+
abi_version    ccache/  qa.log          stamps/    work-shared/
+
buildhistory/  deploy/  saved_tmpdir    sysroots/
+
cache/        pkgdata/  sstate-control/  work/
+
 
+
I'm not sure what all of these are for, but I know the cross-compilers are kept in '''sysroots'''. Go and explore.  See if you can find them.  We'll work with them in a later exercise. What we want is in the '''work''' directory:
+
 
+
host:~/BeagleBoard/oe/build/tmp-angstrom_v2012_05-eglibc$ '''cd work; ls -F'''
+
all-angstrom-linux/            beagleboard-angstrom-linux-gnueabi/
+
armv7a-angstrom-linux-gnueabi/  x86_64-linux/
+
 
+
These directories contain tools based on what they work on.  '''x86_64-linux''', for example, has the tools that run on your host computer.  '''armv7a-angstrom-linux-gnueabi''' has things that run on all arm processors.  '''beagleboard-angstrom-linux-gnueabi''' has things that are Beagle specific, and that's where we find the kernel.
+
 
+
host:~/BeagleBoard/oe/build/tmp-angstrom_v2012_05-eglibc/work$ '''cd beagleboard-angstrom-linux-gnueabi/; ls -F'''
+
linux-mainline-3.2.18-r121b/
+
 
+
It looks like we have the 3.2.18 version of the kernel.  Here's how you find out what kernel version have we've been running on the Beagle.  On the Beagle run:
+
  
 +
If all goes well you will boot into your new kernel.
 
  beagle$ '''uname -a'''
 
  beagle$ '''uname -a'''
  Linux beaglebone 3.2.5+ #1 Mon Feb 13 19:22:44 CET 2012 armv7l GNU/Linux
+
  Linux beaglebone 3.2.25+ #1 Fri Oct 19 11:05:28 EDT 2012 armv7l GNU/Linux
 
+
It looks like we're running the 3.2.5+ kernel. But what if you don't want the most recent kernel? You need to find the bitbake recipe for the kernel you are running.  Here's how I did it, back to the host:
+
 
+
host$ '''cd ~/BeagleBoard/oe'''
+
host$ '''find . -name "*2.6.32*" | grep recipe'''
+
./sources/meta-ti/recipes-kernel/linux/linux-omap-psp-2.6.32
+
./sources/meta-ti/recipes-kernel/linux/linux-omap-psp_2.6.32.bb
+
 
+
The '''find''' command looks for files and directories that contain the string '''2.6.32''', the '''grep''' command then displays only those that contain the string '''recipe''' in the name. What you find is the the name of the recipe for building the kernel we're interested in.  Now all you have to do is bitbake it.  Be sure the '''conf/local.conf''' file is set as described earlier so that the sources aren't deleted.
+
 
+
Note: '''Don't do this just yet.  I'm not sure which version we need.'''
+
 
+
host$ '''source ~/.oe/environment-angstromv2012.05'''
+
host$ '''bitbake linux-omap-psp-2.6.32'''
+
 
+
I think mine took a couple of hours.
+
 
+
== Download and Compile U-boot ==
+
 
+
While were' at it, let's get the boot loader we'll be using...
+
 
+
host$ '''bitbake u-boot'''
+
 
+
Mine took about 8 minutes.
+
 
+
Once installed you are ready for kernel work.
+
 
+
== Installing on a Remote Machine ==
+
 
+
Installing the cross development tools and the kernel on a laptop is nice, but sometimes the downloads are too long for such a portable device.  I've had a bitbake run some 12 hours.  Another option is to use a remote machine.  In my case our CSSE department has created a virtual machine with Ubuntu 12.04 installed on it. 
+
 
+
To install on a remote machine are the same as above;  However here's a couple of tips to make it easier. 
+
 
+
First, ssh to the remote machine.  Assume the machine is called '''csse''' and your login name is '''beagle'''.
+
 
+
local$ ssh -CX beagle@csse
+
 
+
You can leave the '''beagle@''' off if you have the same login on both machine.  The '''-C''' says to compress everything that's moved between the machines over the network.  This is good for slow connections.  The '''X''' says to pass the X11 display information to the remote machine.  This way you can run graphical programs, such as gedit, on the remote machine and the graphics will display on your local machine (assuming you are running X11 on your local machine).
+
 
+
If you are '''ssh'''ing a lot check out the tip [[ECE497_Tips_and_Tricks#Suspending_ssh | here]] about suspending ssh and the tip [[ECE497_Tips_and_Tricks#Authorizing_ssh | here]] about authorizing ssh so you don't have to enter your password every time.
+
 
+
Once logged on to the removed machine run
+
 
+
remote$ sudo apt-get install byobu
+
 
+
This installs '''byobu''' which is a program that lets you connect to the same shell from multiple machines.  Once installed run
+
 
+
remote$ byobu
+
 
+
You'll see something like:
+
 
+
[[File:Screenshot-beagle@ubu-may_-_byobu.png | 300px]]
+
 
+
So what?  Run a couple of commands, like '''ls''' or '''who''', then hit '''F6'''.  This will suspend your session.  Now run '''byobu''' again. You'll be back in the same session. The session keeps running, even when you aren't connected.
+
 
+
Do you see the use?
+
* Fire up byobu
+
* Start a long bitbake
+
* Once you are sure it running OK, hit F6 and go home.
+
* From home fire up byobu and you'll see your bitbake (probably still running). 
+
* You can F6 and check on it later.
+
  
Try opening another terminal and running byobu in both terminals. You'll see the same thing in both.
+
== DAS U-boot ==
 +
These instructions came from [http://www.eewiki.net/display/linuxonarm/Home eewiki].
  
Run
+
=== download ===
 +
While we're at it, let's get the boot loader we'll be using.  It takes some 3 minutes.
  
  $ man byobu
+
  host$ '''cd ~/BeagleBoard'''
 +
host$ '''git clone git://git.denx.de/u-boot.git'''
 +
host$ '''cd u-boot/'''
 +
host$ '''git checkout v2012.10-rc2 -b tmp'''
  
to see what it can doHere's a list of shortcuts:
+
=== compile ===
 +
Now configure and buildThe first time takes some 4 minutes.  After that it's only 5 seconds or so. (Replace '''am335x_evm_config''' with '''omap3_beagle_config''' if you are compiling for the xM.)
 +
host$ '''make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- am335x_evm_config'''
 +
host$ '''make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-'''
  
      F2 - Create a new window
+
=== install ===
      F3 - Move to previous window
+
      F4 - Move to next window
+
      F5 - Reload profile
+
      F6 - Detach from this session
+
      F7 - Enter copy/scrollback mode
+
      F8 - Re-title a window
+
      F9 - Configuration Menu
+
      F12 -  Lock this terminal
+
      Ctrl-a $ - show detailed status
+
      Ctrl-a R - Reload profile
+
      Ctrl-a ! - Toggle key bindings on and off
+
      Ctrl-a k - Kill the current window
+
  
But there is much more. Go and explore.
+
host$ '''scp u-boot.img root@beagle:.'''
 +
beagle$ '''mkdir /media/mmcblk0p1'''
 +
beagle$ '''mount /dev/mmcblk0p1 /media/mmcblk0p1'''
 +
beagle$ '''cd /media/mmcblk0p1'''
 +
beagle$ '''mv u-boot.img u-boot.img.orig'''  # Save the working u-boot
 +
beagle$ '''cp ~/u-boot.img u-boot.img.new'''
 +
beagle$ '''cp u-boot.img.new u-boot.img'''
 +
Once installed you are ready for u-boot work.
  
 
{{YoderFoot}}
 
{{YoderFoot}}

Revision as of 19:28, 5 November 2012

thumb‎ Embedded Linux Class by Mark A. Yoder


Early in the class most of the exercises we will do will all run on the BeagleBoard. You'll be able to edit (gedit), compile (gcc) and run all on the Beagle. Later, when we start compiling the kernel [1] or the boot loader, (U-boot) you will need to cross compile on a Linux machine and copy the results to the Beagle.

The purpose of this exercise is to install all the tools needed for compiling on your host so they will be ready when you need them.

Instructions for building Ångström are given here; however there are a few changes you have to make. Here's what I did.

Tip: Run this exercise using a wired connection if you can. The Ubuntu wireless driver can be finicky, and if it stops working you'll have to restart some of this.

The Kernel

These instructions have been tested for the 3.2.25 kernel.

download

These are notes are based on Beagleboard kernel git site.

First download the tools needed to compile the kernel. This took about 25 seconds.

host$ sudo apt-get install -y git lzop gcc-arm-linux-gnueabi uboot-mkimage

Next download the tools to get the kernel and the patches needed to make it run on the beagle. (2.5 seconds)

host$ cd ~/BeagleBoard
host$ git clone git://github.com/beagleboard/kernel.git
host$ cd kernel
host$ git checkout 6a7c4284a16fed3dae87f4aef78b59c902e4da84 -b beaglebone-3.2

Next download the kernel and the patches. Before running ./patch/sh, take a look at it. Can you figure out what it's doing? Also look at patch_script.sh, it's where the details are. The downloading/patching process takes some 39 minutes.

host$ less patch.sh patch_script.sh
host$ ./patch.sh
host$ cp patches/beaglebone/defconfig kernel/arch/arm/configs/beaglebone_defconfig
host$ wget http://arago-project.org/git/projects/?p=am33x-cm3.git\;a=blob_plain\;f=bin/am335x-pm-firmware.bin\;hb=HEAD -O kernel/firmware/am335x-pm-firmware.bin
host$ md5sum kernel/firmware/am335x-pm-firmware.bin 
17d6a4c24d3cb720aa9ed4522cb891fc  kernel/firmware/am335x-pm-firmware.bin

compile

Once patched you are ready to compile the kernel. The first time takes a while. Mine tool 4 minutes, but I was running on 8 cores. Set the -jX to match the number of cores you have. uImage is the kernel!

host$ cd kernel
host$ make beaglebone_defconfig

Now that you know it's working, let's compile it. First set the paths to find the cross-compiles. Put the following in a file, call it ~/.oe/crossCompile.sh.

export ARCH=arm
export CROSS_COMPILE=arm-linux-gnueabi-

Do the above once

Now source the file.

host$ source ~/.oe/crossCompileEnv.sh

Do the above once per terminal session.

host$ make -j9
host$ make uImage

Do the above every time you recompile the kernel

You also need all the kernel modules. Here we create a directory to install them in. (a few seconds)

host$ mkdir ../rootfs
host$ make INSTALL_MOD_PATH=../rootfs modules_install

install

Copy the kernel and the modules to the Beagle. (a minute or so)

host$ cd ..
host$ scp kernel/arch/arm/boot/uImage root@beagle:/boot/uImage-3.2.25+
host$ cd rootfs
host$ find -H -depth | cpio -o -H crc | ssh root@beagle 'cd /; cpio -id' 

Now log into the beagle and move some things around.

host$ ssh root@beagle

This will copy the kernel to the ext4 partition.

beagle$ cd /boot
beagle$ rm uImage
beagle$ ln -s uImage-3.2.25+ uImage

This will copy to the FAT partition.

beagle$ mkdir /media/mmcblk0p1
beagle$ mount /dev/mmcblk0p1 /media/mmcblk0p1
beagle$ cp /boot/uImage-3.2.25+ /media/uImage

reboot

Make sure screen is running on your host so you can see the shutdown and boot processes.

host$ screen /dev/ttyUSB1 115200

If you get an error try changing making yourself the owner of /dev/ttyUSB1.

host$ sudo chown yoder:yoder /dev/ttyUSB1
host$ screen /dev/ttyUSB1 115200

Then restart you beagle

beagle$ shutdown -r now

If all goes well you will boot into your new kernel.

beagle$ uname -a
Linux beaglebone 3.2.25+ #1 Fri Oct 19 11:05:28 EDT 2012 armv7l GNU/Linux

DAS U-boot

These instructions came from eewiki.

download

While we're at it, let's get the boot loader we'll be using. It takes some 3 minutes.

host$ cd ~/BeagleBoard
host$ git clone git://git.denx.de/u-boot.git
host$ cd u-boot/
host$ git checkout v2012.10-rc2 -b tmp

compile

Now configure and build. The first time takes some 4 minutes. After that it's only 5 seconds or so. (Replace am335x_evm_config with omap3_beagle_config if you are compiling for the xM.)

host$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- am335x_evm_config
host$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-

install

host$ scp u-boot.img root@beagle:.
beagle$ mkdir /media/mmcblk0p1
beagle$ mount /dev/mmcblk0p1 /media/mmcblk0p1
beagle$ cd /media/mmcblk0p1
beagle$ mv u-boot.img u-boot.img.orig  # Save the working u-boot
beagle$ cp ~/u-boot.img u-boot.img.new
beagle$ cp u-boot.img.new u-boot.img

Once installed you are ready for u-boot work.




thumb‎ Embedded Linux Class by Mark A. Yoder