FaqEldk50Beta < DULG

---+!! ELDK 5.0 Beta Testing

%TOC%

ELDK Release 5.0 is based on the [[http://www.yoctoproject.org/][Yokto Project]], a complete embedded Linux development environment with tools, metadata, and documentation - everything you need - driven and supported by the [[http://www.linuxfoundation.org/news-media/announcements/2011/03/yocto-project-aligns-technology-openembedded-and-gains-corporate-co][Linux Foundation]].

As the Yocto project is nearing it's release 1.0,
[[https://wiki.pokylinux.org/wiki/Yocto_1.0_Schedule][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
The beta images are currently available in the ="beta-eldk/"=
directory of the DENX FTP server.
We recommend to always use the latest available snapshot build.
Please contact
[[mailto:info@denx.de?subject=Please%20send%20ELDK%20Beta%20access%20data][DENX]]
for access data.
<verbatim>
$ 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                Apr  7 10:54   1.0+snapshot-20110406
drwxr-xr-x                Jan 28 10:40   twister
ncftp / > cd 1.0+snapshot-20110406
OK. Current directory is /1.0+snapshot-20110406
ncftp /1.0+snapshot-20110406 > dir
-rwxrw-r--    207565495   Apr  6 17:51   poky-eglibc-i686-arm-toolchain-gmae-1.0+snapshot-20110406.tar.bz2
-rwxr--r--    193388845   Apr  7 10:41   poky-image-sato-sdk-qemuarm-20110407060156.rootfs.tar.bz2
ncftp /1.0+snapshot-20110406 > bin
ncftp /1.0+snapshot-20110406 > get poky*
</verbatim>
Here ="poky-eglibc-i586-arm-toolchain-*"= is the cross tool chain for
ARM targets and x86 hosts,
while "poky-image-*-qemuarm-*.rootfs.tar.bz2"= is a root file system
image for ARM boards.

---++ Installation
As mentioned above, at this point of time there is neither a skin nor
installation tools to provide the familiar ELDK look and feel yet.
Installation has to be done manually instead.
Also, at this point, installation has to be done into the
="/opt/poky/"= directory:
   * Create necessary directories:
     <verbatim>
$ sudo mkdir /opt/poky
$ sudo chmod 01777 /opt/poky
$ mkdir /opt/poky/root-arm
     </verbatim>
   * Install cross tool chain:
     <verbatim>
$ cd /
$ tar xpf /tmp/poky-eglibc-i586-arm-toolchain-*
     </verbatim>
     *Note:* Do *not* run this step as user =root=,
     run it as a normal user instead!
     %BR%
     You may see a number of warnings and error messages, for example:
     <verbatim>
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
     </verbatim>
     These messages are due to the currently used installation method
     and can safely be ignored.
   * Install target root file system:
     <verbatim>
$ cd /opt/poky/root-arm
$ sudo tar xpf /tmp/poky-image-*
     </verbatim>
---++ Using the Cross Tools
   * Prepare environment variables:
     <verbatim>
$ export PATH=/opt/poky/*snapshot/sysroots/i586-pokysdk-linux/usr/bin/armv5te-poky-linux-gnueabi:$PATH
$ export ARCH=arm
$ export CROSS_COMPILE=arm-poky-linux-gnueabi-
     </verbatim>
   * Use it to build U-Boot:
     <verbatim>
$ cd ~/git/u-boot
$ ./MAKEALL omap3_beagle
     </verbatim>
   * Use it to build Linux:
     <verbatim>
$ cd ~/git/linux
$ make davinci_all_defconfig
$ make -j4 -s uImage
     </verbatim>

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:
     <verbatim>
/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
     </verbatim>
   * Fix the following line in ="/etc/inittab"= :
     <verbatim>
S:2345:respawn:/sbin/getty 115200 ttyAMA0
     </verbatim>
     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.