Get started with ubuntu on omap4

From OMAPpedia

Revision as of 14:19, 6 March 2012 by Jeremiah (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This page describes the steps to get started with Ubuntu on OMAP4. These instructions apply to the OMAP4 blaze board. These instructions were first written some time ago, so some of this information may be out of date.

After reading this page, you shall have a live and running Ubuntu File-system on your OMAP4 platform. The standard setup guides you to install the bootloaders, kernel and file-system to a SD card, and boot into it.

Note that these instructions will direct you to fetch code from TI repositories.


[edit] Preliminary settings

[edit] Tool-chain

The below instructions suppose that you will be cross-compiling from a Ubuntu (x86) host, using the CodeSourcery tool-chain. It is advised to use a recent tool-chain like the 2010-q1-202 (gcc 4.4.1). The path to the CodeSourcery binaries shall be added to the $PATH environment variable.

[edit] Workstation

The instructions on this page have been verified on a Ubuntu workstation running Lucid (Karmic or older Ubuntu versions may also work)

[edit] SD card capacity

A Ubuntu file-system with a graphical interface (UNE for example), requires at least a 4GB SD card. A smaller SD card is sufficient if you do not need to install a graphical interface.

[edit] Bootloaders

OMAP4 uses u-boot + x-loader to get the platform booted. Detailed information on how this works is detailed here:

The OMAP4 dedicated instructions are described below:

mkdir bootloader
cd bootloader
git clone git://
cd u-boot
git tag -l
git checkout <latest L24.x tag>
make ARCH=arm distclean
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap4430sdp_config
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

=> Generates: ./u-boot.bin

cd ..
git clone git:// 
cd x-loader
git checkout <latest L24.x tag>

(note that both u-boot and x-loader folders must be at the same directory level)

make ARCH=arm distclean 
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- omap4430sdp_config 
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- ift

=> Generates ./MLO

The generated MLO and u-boot.bin files will have to be copied on the SD card.

Note: To get the list of L24.x tags, once in the cloned u-boot or x-loader folder, type:

git tag | grep L24

[edit] Ubuntu kernel

See Ubuntu kernel for OMAP4 dedicated pages: Ubuntu kernel for OMAP4

[edit] Ubuntu file-system step 1: minimal file system generation

The current easiest way to get a Ubuntu file-system, is to generate it using the 'rootstock' tool.

The raw process (which is described in more details here after) is in 2 steps: > Generate a basic image using the rootstock Ubuntu tool > Boot on this basic file-system and install additional packages

The 1st step is discussed in this chapter.

Rootstock is a tool running on a Ubuntu host, relying on qemu, that permits to generate Ubuntu FS.

(Pre-requisites to generate Lucid images: Ubuntu workstation connected to internet with Karmic (09.10) or more recent Ubuntu release installed.)

sudo apt-get install rootstock
sudo rootstock -d lucid -f ubuntu -l ubuntu -p ubuntu --serial ttyO2 --locale en_US.UTF-8 -s ubuntu-minimal,openssh-server,nano

Note that openssh-server and nano packages are just added for convenience.

=> will generate a tgz images containing a basic FS.

[edit] SD card preparation

Examples commands to achieve this, assuming the SD card is seen as /dev/sdc on your Ubuntu workstation (and the script to prepare the SD card is called ''):

sudo /dev/sdc
sudo mkdir /mnt/mmc1
sudo mount /dev/sdc1 /mnt/mmc1
sudo mkdir /mnt/mmc2
sudo mount /dev/sdc2 /mnt/mmc2
sudo cp MLO /mnt/mmc1/
sudo cp u-boot.bin /mnt/mmc1/
sudo cp uImage /mnt/mmc1/
cd /mnt/mmc2
sudo tar xzf <path to basic rootFS generated>
sudo cp <generated linux-image*.deb file> /home/ubuntu
cd -
sudo umount /mnt/mmc1
sudo umount /mnt/mmc2

[edit] Boot the board

At this stage, the SD card can be plugged into the OMAP4 board. Also connect the USB for serial console and terminal: this USB connector provides access to 4 serial ports. The 3rd one is used for the console/terminal.

Now switch-on the board. You shall get to the u-boot prompt and get a chance to interrupt the countdown.

The default bootargs embedded into u-boot may not enable you to boot directly from SD cardand for a ubuntu file-system. You shall set some u-boot environment variables to fix this. Type the following at the u-boot prompt:

setenv bootargs console=ttyO2,115200n8 noinitrd mem=512M root=/dev/mmcblk0p2 rootdelay=1 ip=dhcp
mmcinit 0; fatload mmc 0 0x80500000 uImage; bootm 80500000


Once booted, you can log in console using user: ubuntu / password: ubuntu.

[edit] Ubuntu file-system step 2: Install packages + customization

At this stage, a minimal Ubuntu filesystem is already up and running. It can be used as any Ubuntu running device (same commands set and setup).

This last step shows how to install the UI, and some useful customizations.

[edit] Image customization tips

[edit] Add multiverse to the repository list

Update packages repository list: add 'multiverse' at the end of the line in /etc/apt/sources.list, and then sudo apt-get update

[edit] proxy setting

If you connect behind a firewall, you may want to setup going through a proxy:

http_proxy="<proxy path>"
 Defaults        env_reset
+Defaults        env_keep="http_proxy no_proxy ftp_proxy https_proxy"

[edit] Ubuntu Netbook Edition file system creation

The UNE file-system cannot be installed directly from rootstock, this is why we need to install it in this 2nd step. Basically, it consists in upgrading the minimal file-system by installing the UNE package.

Moreover, it is not possible today to boot a UNE file-system over NFS (boot over NFS is possible with non-graphical file-systems).

sudo apt-get install ubuntu-netbook

This can be quite long as many package are installed.


(If you created your file-system with a different user-name, replace 'ubuntu' by this user name)

load-module module-console-kit

Type the following command on the target:

sudo gconftool-2 --direct  --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set /apps/gnome-screensaver/lock_enabled false

or ensure the file /etc/gconf/gconf.xml.mandatory/%gconf-tree.xml contains at least the following entry:

<?xml version="1.0"?>
        <dir name="apps">
                <dir name="gnome-screensaver">
                        <entry name="lock_enabled" mtime="946685422" type="bool" value="false"/>

From the host, insert the SD card hosting the root file-system, and mount the partition hosting the root file-system. Go to the FS root and type:

sudo tar c . | gzip -c > <path and name to a root-FS tarball>.tar.gz
Personal tools