Difference between revisions of "User:B-flat"

From Gumstix User Wiki
Jump to: navigation, search
(Building an Rootfs image and a kernel)
Line 15: Line 15:
  
 
First I checked out a copy of ([http://www.gumstix.net/Software/view/Getting-started/Setting-up-a-build-environment/111.html instructions]) the Verdex build system. So the home directory now has:
 
First I checked out a copy of ([http://www.gumstix.net/Software/view/Getting-started/Setting-up-a-build-environment/111.html instructions]) the Verdex build system. So the home directory now has:
~/gumstix/gusmtix-oe/
+
~/gumstix/gusmtix-oe/
~/overo-oe/
+
~/overo-oe/
  
 
Then, I copied the Verdex image recipes to the user.collection.
 
Then, I copied the Verdex image recipes to the user.collection.
mkdir -p ~/overo-oe/user.collection/images/
+
mkdir -p ~/overo-oe/user.collection/images/
cp ~/gumstix/gumstix-oe/com.gumstix.collection/packages/images/* ~/overo-oe/user.collection/images/
+
cp ~/gumstix/gumstix-oe/com.gumstix.collection/packages/images/* ~/overo-oe/user.collection/images/
  
baking gumstix-basic-image I ran into problems with No GNU_HASH fount in elf for the i2c and pxaregs recipes. Thanks to help from the gumstix-users mailing list I managed to get around it. Basically both the i2c and the pxaregs recipes compiled the source code directly in the i2c.bb and pxaregs.bb files but didn't use the LDFLAGS at all. So I added ${LDFLAGS} to the end of the line in the respective recipes and then the baking went fine.
+
Once copied, I ran:
 +
bitbake gumstix-basic-image
  
Currently, I boot the gumstix from a 2GB micro SD card. (found out that 4GB SDHC is not supported by the U-boot config, for booting, but when booted its no problem).
+
Resulting in a failure and Bitbake reporting that nothing provides some package and exited without building anything. I then copied the recipes for those packages and ran bitbake again. At the end I had copied:
However, the boot sequence hands at I2C dev ... something.
+
task-base-gumstix
 +
motd
 +
uisp
 +
version
 +
www-content
 +
 
 +
==Problems with No GNU_HASH fount in elf ==
 +
 
 +
Baking the gumstix-basic-image the process stopped with the I2C package and the log information boiled down to the error message: No GNU_HASH fount in elf for the i2c.
 +
 
 +
Asking for hints in the gumstix.users mailing list helped alot. Thanks Koen and Philip (archive [http://www.nabble.com/No-GNU_HASH-found-in-elf-binary-td23072960.html here]) and I could find the problem in the i2c.bb file:
 +
The task do_compile ignored the LDFLAGS set by the oe/autoconf tools.
 +
do_compile () {
 +
        ${CC} -o i2c *.c
 +
}
 +
 
 +
Adding ${LDFLAGS} to the line for compiling solved this problem:
 +
do_compile () {
 +
        ${CC} -o i2c *.c ${LDFLAGS}
 +
}
 +
 
 +
Then the same problem emerged in the pxaregs recipes and the same solution applied. This resulted in a completed bake.
 +
 
 +
==Booting the gumstix from a micro SD card==
 +
 
 +
Currently, I boot the gumstix from a 2GB micro SD card. NOTE that 4GB SDHC does work to boot from. If booting from flash, the card is found and read/write works fine even with 4GB. Probably the U-boot version does not support SDHC cards.
 +
These [http://www.gumstix.net/User/view/User-how-to-s/Booting-from-microSD/SD/MMC/110.html instructions] for setting up the MicroSD card works fine for me.
 +
 
 +
Current status is that the boot is started OK, but the boot sequence hangs at I2C dev ... something. :(

Revision as of 06:21, 19 April 2009

Introduction

I am working on settin up my Verdex Pro 400-Bt with LCD to run java with the touch screen and a simple graphical gui.

I'll use this page to share my experiencs on successes and obstacles I find. Feedback always appreciated.

My Build system

I am running a VM-ware player image with Gentoo Linux placed on a USB hostpowered disc. This does not give highest possible performance, but it allows for a lot of mobility and portability. Peripherals like a (micro)SD-card reader adapter for USB works fine, but the built-in one in my laptop is not available within the VM-ware player.

On my Gentoo linux I set-up the build environment according to the instructions for the overo build system.

The reason for choosing the open-embedded as for Overo is that the Verdex buildsystem has not been updated for approx. a year now and I wanted the latest recipes to get e.g. Open JDK.

Building an Rootfs image and a kernel

First I checked out a copy of (instructions) the Verdex build system. So the home directory now has:

~/gumstix/gusmtix-oe/
~/overo-oe/

Then, I copied the Verdex image recipes to the user.collection.

mkdir -p ~/overo-oe/user.collection/images/
cp ~/gumstix/gumstix-oe/com.gumstix.collection/packages/images/* ~/overo-oe/user.collection/images/

Once copied, I ran:

bitbake gumstix-basic-image

Resulting in a failure and Bitbake reporting that nothing provides some package and exited without building anything. I then copied the recipes for those packages and ran bitbake again. At the end I had copied:

task-base-gumstix
motd
uisp
version
www-content

Problems with No GNU_HASH fount in elf

Baking the gumstix-basic-image the process stopped with the I2C package and the log information boiled down to the error message: No GNU_HASH fount in elf for the i2c.

Asking for hints in the gumstix.users mailing list helped alot. Thanks Koen and Philip (archive here) and I could find the problem in the i2c.bb file: The task do_compile ignored the LDFLAGS set by the oe/autoconf tools.

do_compile () {
       ${CC} -o i2c *.c
}

Adding ${LDFLAGS} to the line for compiling solved this problem:

do_compile () {
       ${CC} -o i2c *.c ${LDFLAGS}
}

Then the same problem emerged in the pxaregs recipes and the same solution applied. This resulted in a completed bake.

Booting the gumstix from a micro SD card

Currently, I boot the gumstix from a 2GB micro SD card. NOTE that 4GB SDHC does work to boot from. If booting from flash, the card is found and read/write works fine even with 4GB. Probably the U-boot version does not support SDHC cards. These instructions for setting up the MicroSD card works fine for me.

Current status is that the boot is started OK, but the boot sequence hangs at I2C dev ... something. :(