GPE Application Development Questions

GPE Application Development Questions

[NBeing]

The "angstrom-2008.1-test-20090104-armv5te-linux-gnueabi-toolchain-gpe.tar.bz2" 
sets up the environment like so:

export PATH=/usr/local/angstrom/arm/bin:$PATH

export PKG_CONFIG_SYSROOT_DIR=/usr/local/angstrom/arm/arm-angstrom-linux-
gnueabi

export PKG_CONFIG_PATH=/usr/local/angstrom/arm/arm-angstrom-linux-
gnueabi/usr/lib/pkgconfig

export CONFIG_SITE=/usr/local/angstrom/arm/site-config

alias opkg='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib 
/usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/etc/opkg-
sdk.conf -o /usr/local/angstrom/arm'

alias opkg-target='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib 
/usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/arm-angstrom-
linux-gnueabi/etc/opkg.conf -o /usr/local/angstrom/arm/arm-angstrom-linux-
gnueabi'



I'm using an "angstrom-2009.X-test-XXXX" image so believe I need to build my 
own toolchain.  I built the image with the latest OE and everything runs on the 
board, however, I'm unable to build the simple "gpe-hello" app.  I believe the 
problem has to do with my mapping of the above paths.  This is what I have, 
would someone be able to confirm, fix, give advance on what I have wrong with 
them?  Or a different way/tutorial I should be following on GPE Application 
Developemnt?  Basically I used the "cross" folder when I could, then staging, 
then rootfs.

export PATH=${HOME}/oe/build/tmp/cross/armv5te/bin:$PATH

export PKG_CONFIG_SYSROOT_DIR=${HOME}/oe/build/tmp/cross/armv5te/arm-angstrom-
linux-gnueabi

export PKG_CONFIG_PATH=${HOME}/oe/build/tmp/staging/armv5te-angstrom-linux-
gnueabi/usr/lib/pkgconfig

export CONFIG_SITE= ???? (Left Out)

alias opkg='LD_LIBRARY_PATH=${HOME}/oe/build/tmp/cross/armv5te/lib 
${HOME}/oe/build/tmp/rootfs/x11-image/usr/bin/opkg-cl -f 
${HOME}/oe/build/tmp/staging/i686-linux/etc/opkg-sdk.conf -o 
${HOME}/oe/build/tmp/cross/armv5te'

alias opkg-target='LD_LIBRARY_PATH=${HOME}/oe/build/tmp/cross/armv5te/lib 
${HOME}/oe/build/tmp/rootfs/x11-image/usr/bin/opkg-cl -f 
${HOME}/oe/build/tmp/rootfs/x11-image/etc/opkg.conf -o 
${HOME}/oe/build/tmp/cross/armv5te/arm-angstrom-linux-gnueabi'



Also while I'm here, in the deploy directory there is a "modules-2.6.28-r9-
at91sam9261ek.tgz" file build, however, I'm unsure what I'm suppose to do with 
it?  If I'm suppose to flash it to my board where would I find the address to 
flash too?  Thanks

Re: GPE Application Development Questions

[Denys Dmytriyenko]

On Thu, Jun 04, 2009 at 11:56:15PM +0000, NBeing wrote:
> The "angstrom-2008.1-test-20090104-armv5te-linux-gnueabi-toolchain-gpe.tar.bz2" 
> sets up the environment like so:
> 
> export PATH=/usr/local/angstrom/arm/bin:$PATH
> 
> export PKG_CONFIG_SYSROOT_DIR=/usr/local/angstrom/arm/arm-angstrom-linux-
> gnueabi
> 
> export PKG_CONFIG_PATH=/usr/local/angstrom/arm/arm-angstrom-linux-
> gnueabi/usr/lib/pkgconfig
> 
> export CONFIG_SITE=/usr/local/angstrom/arm/site-config
> 
> alias opkg='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib 
> /usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/etc/opkg-
> sdk.conf -o /usr/local/angstrom/arm'
> 
> alias opkg-target='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib 
> /usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/arm-angstrom-
> linux-gnueabi/etc/opkg.conf -o /usr/local/angstrom/arm/arm-angstrom-linux-
> gnueabi'
> 
> 
> 
> I'm using an "angstrom-2009.X-test-XXXX" image so believe I need to build my 
> own toolchain.  I built the image with the latest OE and everything runs on the 
> board, however, I'm unable to build the simple "gpe-hello" app.  I believe the 
> problem has to do with my mapping of the above paths.  This is what I have, 
> would someone be able to confirm, fix, give advance on what I have wrong with 
> them?  Or a different way/tutorial I should be following on GPE Application 
> Developemnt?  Basically I used the "cross" folder when I could, then staging, 
> then rootfs.
> 
> export PATH=${HOME}/oe/build/tmp/cross/armv5te/bin:$PATH
> 
> export PKG_CONFIG_SYSROOT_DIR=${HOME}/oe/build/tmp/cross/armv5te/arm-angstrom-
> linux-gnueabi
> 
> export PKG_CONFIG_PATH=${HOME}/oe/build/tmp/staging/armv5te-angstrom-linux-
> gnueabi/usr/lib/pkgconfig
> 
> export CONFIG_SITE= ???? (Left Out)
> 
> alias opkg='LD_LIBRARY_PATH=${HOME}/oe/build/tmp/cross/armv5te/lib 
> ${HOME}/oe/build/tmp/rootfs/x11-image/usr/bin/opkg-cl -f 
> ${HOME}/oe/build/tmp/staging/i686-linux/etc/opkg-sdk.conf -o 
> ${HOME}/oe/build/tmp/cross/armv5te'
> 
> alias opkg-target='LD_LIBRARY_PATH=${HOME}/oe/build/tmp/cross/armv5te/lib 
> ${HOME}/oe/build/tmp/rootfs/x11-image/usr/bin/opkg-cl -f 
> ${HOME}/oe/build/tmp/rootfs/x11-image/etc/opkg.conf -o 
> ${HOME}/oe/build/tmp/cross/armv5te/arm-angstrom-linux-gnueabi'

The whole point of the toolchain/SDK is to be able to build apps 
like "gpe-hello" w/o having OE around, i.e. w/o cross, staging or rootfs.

> Also while I'm here, in the deploy directory there is a "modules-2.6.28-r9-
> at91sam9261ek.tgz" file build, however, I'm unsure what I'm suppose to do with 
> it?  If I'm suppose to flash it to my board where would I find the address to 
> flash too?  Thanks

That's just a tarball with kernel modules. They should already be in your 
filesystem image.

-- 
Denys

Re: GPE Application Development Questions

[NBeing]

Denys Dmytriyenko <denis <at> denix.org> writes:

>
> The whole point of the toolchain/SDK is to be able to build apps 
> like "gpe-hello" w/o having OE around, i.e. w/o cross, staging or rootfs.
> 

Ahh I see.  I was able to make a simple bitbake recipe to compile the gpe-hello 
app and it works on the board.  I'm still interested in compiling manually 
though.

I ran the "bitbake meta-toolchain" recipe and it completed with no errors.  It 
generates two files "angstrom-2009.X-test-20090609-armv5te-linux-gnueabi-
toolchain.tar.bz2" and "angstrom-2009.X-test-20090609-armv5te-linux-gnueabi-
toolchain-extras.tar.bz2".  The -extras file seems to be empty.

I extract the non-empty *.tar.bz2 into my "/usr" directory and sourced the 
environment-setup file.  All the paths seems to get set correctly, except one.  
The "$PKG_CONFIG_PATH" variable gets set to the below:
/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib/pkgconfig

However, the "pkgconfig" directory in "...gnueabi/usr/lib/" doesn't exists.  In 
fact there isn't any relevant *.pc in *.tar.bz2...  Would anyone have run into 
this problem before?  I checked the toolchain online and it does have this 
folder.

Is there any log files I can supply that would help, or something someone can 
suggest I try.  If you issue the following commands you'll probably see the 
problem yourself:

Edit local.conf to set "at91sam9261ek", use latest dev branch + set env vars.
bitbake x11-image
bitbake meta-toolchain
Look in the resulting .../sdk/*.tar.bz2 package for the above folder.

Thanks