Difference between revisions of "User:B-flat"
(→Building an Rootfs image and a kernel) |
|||
Line 14: | Line 14: | ||
== Building an Rootfs image and a kernel== | == Building an Rootfs image and a kernel== | ||
− | 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. | + | 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/ | ||
+ | ~/overo-oe/ | ||
− | Then, I copied the com.gumstix. | + | 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/ | ||
− | |||
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. | 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. | ||
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). | 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). | ||
However, the boot sequence hands at I2C dev ... something. | However, the boot sequence hands at I2C dev ... something. |
Revision as of 05:53, 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/
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.
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). However, the boot sequence hands at I2C dev ... something.