On 26/01/12 15:24, Gary Thomas wrote:
On 2012-01-26 08:07, Gary Thomas wrote:
On 2012-01-26 07:06, Gary Thomas wrote:
On 2012-01-26 06:50, Jack Mitchell wrote:
On 26/01/12 13:27, Gary Thomas wrote:
On 2012-01-26 05:35, Gary Thomas wrote:
On 2012-01-26 05:01, Jack Mitchell wrote:
On 26/01/12 12:00, Koen Kooi wrote:
Op 26 jan. 2012, om 12:06 heeft Jack Mitchell het volgende
geschreven:
Hello everyone,
I will soon be receiving a Beaglebone and I wish to transfer
the work I have been doing with Yocto on the Beagleboard over
to the Beaglebone, to show my company how the same
application codebase can be run different platforms using
Linux/Yocto/etc..
I have been looking at the meta-ti layer and trying to figure
out how it works and how I will integrate it into the yocto
build environment, but I thought I would just throw a
query out to see if anybody is doing this and if there are any
pitfalls I should avoid.
There's a README in the meta-ti layer, follow the instructions
in there.
Hi Koen,
I understand that there is a readme in the meta-ti layer however
this refers specifically to using Angstrom and associated
layers, where as I want to build specifically for
yocto.
So I was looking for pointers for abstracting the meta-ti layer
form angstrom over to Yocto.
I gave this a try, just adding the meta-ti layer into my stack.
Sadly, it blew up right away with this error:
ERROR: Failure expanding variable FILESPATH, expression was
${@base_contains('DISTRO_FEATURES', 'tipspkernel',
"/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/linux-gnueabi:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/arm:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/build-linux:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/pn-linux-ti33x-psp:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/beaglebone:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/armv7a:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/amltd:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/forcevariable:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/${FEED_ARCH}:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/ti33x:/home/local/poky-multi/meta-ti/recip
e
s
-
k
e
rn
el/linux/linux-ti33x-psp-3.1/tipspkernel/libc-glibc:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1/tipspkernel/:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/linux-gnueabi:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/arm:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/build-linux:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/pn-linux-ti33x-psp:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/beaglebone:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/armv7a:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/amltd:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/forcevariable:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/${FEED_ARCH}:/home/local/poky-multi/met
a
-
t
i
/
re
cipes-kernel/linux/linux-ti33x-psp/tipspkernel/ti33x:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/libc-glibc:/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp/tipspkernel/:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/linux-gnueabi:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/arm:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/build-linux:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/pn-linux-ti33x-psp:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/beaglebone:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/armv7a:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/amltd:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/forcevariable:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/${FEED_ARCH}:/home/local/poky-multi/meta-
t
i
/
r
e
ci
pes-kernel/linux/files/tipspkernel/ti33x:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/libc-glibc:/home/local/poky-multi/meta-ti/recipes-kernel/linux/files/tipspkernel/:",
"", d)}${@base_set_filespath([
"/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1-r0",
"/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1",
"/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp",
"/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.1",
"/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp",
"/home/local/poky-multi/meta-ti/recipes-kernel/linux/files",
"/home/local/poky-multi/meta-ti/recipes-kernel/linux" ], d)}
which triggered exception SyntaxError: EOL while
scanning
string literal (FILESPATH, line 1)
ERROR: Command execution failed: Exited with 1
I'm not sure what this means or how to diagnose what's wrong.
I worked past this. I turns out that my <DISTRO>.conf file had
this line in it (needed by some of the OLD meta-texasinstruments
recipes):
OVERRIDES .= ":${FEED_ARCH}:${SOC_FAMILY}"
I took out the FEED_ARCH and now I'm getting farther.
Next hurdle:
Could not include required file
recipes-images/angstrom/systemd-image.bb
n.b. I have done the same thing successfully before with the
Angstrom meta-texasinstruments layer (which I know has been
deprecated and replaced by meta-ti), so I know the process can
work.
From a clean poky edison build directory with machine_beagleboard
selected and the meta-ti layer enabled last in my bblayers conf I
receive this error:
ERROR: Could not inherit file classes/systemd.bbclass
However I cannot find where this is being called from in the
meta-ti layer.. it seems very similar to what Gary has run into...
Try adding this to local.conf
BBMASK = ".*/meta-ti/recipes-misc/"
This will let bitbake skip the troublesome recipes. Since you're
interested in building Yocto, it should be OK.
Next, problem: I tried to build for my BeagleBone, but the kernel
build failed with this error:
| arch/arm/boot/compressed/head.S: Assembler messages:
| arch/arm/boot/compressed/head.S:127: Error: selected processor does
not support requested special purpose register -- `mrs r2,cpsr'
| arch/arm/boot/compressed/head.S:134: Error: selected processor does
not support requested special purpose register -- `mrs r2,cpsr'
| arch/arm/boot/compressed/head.S:136: Error: selected processor does
not support requested special purpose register -- `msr cpsr_c,r2'
| make[2]: *** [arch/arm/boot/compressed/head.o] Error 1
| make[2]: *** Waiting for unfinished jobs....
| make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
| make: *** [uImage] Error 2
| ERROR: oe_runmake failed
NOTE: package linux-ti33x-psp-3.1-r0: task do_compile: Failed
ERROR: Task 352
(/home/local/poky-multi/meta-ti/recipes-kernel/linux/linux-ti33x-psp_3.1.bb,
do_compile) failed with exit code '1'
Looks like an incompatibility with the tools
Angstrom = gcc-cross-4.5-r45+svnr181733
Yocto = gcc-cross-4.6.2+svnr181430-r20
Or possibly:
Angstrom = binutils-cross-2.20.1-r9
Yocto = binutils-cross-2.22-r2
Oh well...
So are these pre-compiled binaries that cannot be linked... or something
along those lines?
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
