ELDK 5.0 Beta Testing

ELDK Release 5.0 is based on the Yokto Project, a complete embedded Linux development environment with tools, metadata, and documentation - everything you need - driven and supported by the Linux Foundation.

As the Yocto project is nearing it's release 1.0, scheduled for Apr 6, 2011, we follow it's progress and provide snapshot builds for testing purposes.

ELDK Release 5.0 will then be based on Yocto Release 1.0, adding packaging and installation tools as you are used from previous ELDK versions.

At the moment, only the raw snapshot builds are available, so there is a little manual action needed for installation and use:

Download the ELDK beta images

$ ncftp -u eldk-beta ftp://ftp.denx.de/
Password: ***********
...
ncftp / > dir
drwxr-xr-x                Jan 12 23:45   0.9
drwxr-xr-x                Jan 18 11:03   0.9+snapshot-20110116
drwxr-xr-x                Jan 31 22:30   0.9+snapshot-20110131
drwxr-xr-x                Feb  3 10:46   0.9+snapshot-20110202
drwxr-xr-x                Jan 28 10:40   twister
ncftp / > cd 0.9+snapshot-20110202
OK. Curncftp /0.9+snapshot-20110202 > dir
-rwxrw-r--    183175473   Feb  2 23:32   poky-eglibc-i586-arm-toolchain-gmae-0.9+snapshot-20110202.tar.bz2
-rwxrw-r--    201440595   Feb  2 20:58   poky-image-sato-sdk-qemuarm-20110202114043.rootfs.tar.bz2
rent directory is /0.9+snapshot-20110202
ncftp /0.9+snapshot-20110202 > bin
ncftp /0.9+snapshot-20110202 > get poky*

Installation

• Create necessary directories:

  $ sudo mkdir /opt/poky
  $ sudo chmod 01777 /opt/poky
  $ mkdir /opt/poky/root-arm
  

• Install cross tool chain:

  $ cd /
  $ tar xpf /tmp/poky-eglibc-i586-arm-toolchain-*
  

  Note: Do not run this step as user root, runit as a normal user instead!
  You may see a number of warnings and error messages, for example:

  tar: ./opt/poky: Cannot utime: Operation not permitted
  tar: ./opt/poky: Cannot change mode to rwxrwxr-x: Operation not permitted
  tar: ./opt: Cannot utime: Operation not permitted
  tar: ./opt: Cannot change mode to rwxrwxr-x: Operation not permitted
  tar: .: Cannot utime: Operation not permitted
  tar: .: Cannot change mode to rwxrwxr-x: Operation not permitted
  tar: Exiting with failure status due to previous errors
  

  These messages are due to the currently used installation method and can safely be ignored.
• Install target root file system:

  $ cd /opt/poky/root-arm
  $ sudo tar xpf /tmp/poky-image-*
  

Using the Cross Tools

• Prepare environment variables:

  $ export PATH=/opt/poky/0.9+snapshot/sysroots/i586-pokysdk-linux/usr/bin/armv5te-poky-linux-gnueabi:$PATH
  $ export ARCH=arm
  $ export CROSS_COMPILE=arm-poky-linux-gnueabi-
  

• Use it to build U-Boot:

  $ cd ~/git/u-boot
  $ ./MAKEALL omap3_beagle
  

• Use it to build Linux:

  $ cd ~/git/linux
  $ make davinci_all_defconfig
  $ make -j4 -s uImage
  

Compared to builds with older tool chain versions you will probably see an increased number of compiler warnings, eventually even new error messages. This is usually because of the new compiler versions used in ELDK 5.0 perform much stricter syntax checking. You may also notice somewhat smaller binary sizes - they also provide better optimizations.

Using the Target Root File System

To be able to use the provided file system as root file system exported over NFS, the following adjustments are needed:

• Replace the pretty generic "/etc/fstab" file with this:

  /dev/nfs   /      nfs   defaults   0 0
  none      /proc      proc   defaults   0 0
  devpts      /dev/pts   devpts   mode=0620,gid=5   0 0
  sysfs      /sys      sysfs   defaults   0 0
  usbdevfs   /proc/bus/usb   usbdevfs noauto      0 0
  tmpfs      /var/volatile   tmpfs   defaults   0 0
  tmpfs      /media/ram   tmpfs   defaults   0 0
  

• Fix the following line in "/etc/inittab" :

  S:2345:respawn:/sbin/getty 115200 ttyAMA0
  

  Replace the string "ttyAMA0" with the correct name of your console device, for example "ttyS0".
• You may want to tweak a few other files, like "/etc/matchbox/session", "/etc/X11/Xserver", "/etc/hostname", "/usr/lib/ts/input.so", etc., depending on your board configuration (is there a LCD with touch screen or not?), etc.