[yocto] [Yocto] general question about how certain features get processed into packages
Hi, This might be a newbie question but i have not yet found the answer in the documentation. So let's say I want to know what core-image-core has as packages ... then I found the following trace back: -Core-image-core.bb uses core-image-base.bb with X11 variables ==> both use core-image.bbclass -Core-image.bbclass defines the tasks that needs to be done for core-image-core.bb o Task-core-apps-console o Task-core-x11-base o Apps-x11-core ==> task-core-apps-x11-core o Package management ==> ... o Task-core-boot o Task-base-extended o Use image.bbclass Now my question is, where can I find what for example task-core-apps-console exactly is as package collection? Since this is a core task list I thought I would find it in /meta/recipes-core/tasks but no luck, I did find task-core-boot there but that is it ... Thanks in advance, Kind regards, Tim ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Yocto] general question about how certain features get processed into packages
On 31 July 2012 10:15, Tim Verstraete wrote: > Now my question is, where can I find what for example task-core-apps-console > exactly is as package collection? Since this is a core task list I thought I > would find it in /meta/recipes-core/tasks but no luck, I did find > task-core-boot there but that is it … On master at least, meta/recipes-core/tasks/tasks-core-console.bb defines a package called task-core-apps-console and specified the runtime dependencies of it. In any case, git grep is your friend. :) Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Yocto] general question about how certain features get processed into packages
Yes, i found that one but task-core-apps-console is not the same as tasks-core-console.bb I would think because in task-core-console.bb they again refer to the one I am looking for: task-core-apss-console ... Kind regards, Tim -Original Message- From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: dinsdag 31 juli 2012 11:31 To: Tim Verstraete Cc: yocto@yoctoproject.org Subject: Re: [yocto] [Yocto] general question about how certain features get processed into packages On 31 July 2012 10:15, Tim Verstraete wrote: > Now my question is, where can I find what for example > task-core-apps-console exactly is as package collection? Since this is > a core task list I thought I would find it in /meta/recipes-core/tasks > but no luck, I did find task-core-boot there but that is it … On master at least, meta/recipes-core/tasks/tasks-core-console.bb defines a package called task-core-apps-console and specified the runtime dependencies of it. In any case, git grep is your friend. :) Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 2012-07-30 13:11, Gary Thomas wrote:
On 2012-07-30 12:49, Jim Abernathy wrote:
On 07/30/2012 01:16 PM, Gary Thomas wrote:
On 2012-07-30 11:09, Jim Abernathy wrote:
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal for the machine
"pandaboard". Besides the basics, I put in a license statement for cloud9 into
local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "5"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
"
The error I'm getting is:
ERROR: ParseError at /home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5:
Could not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= "1.15.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "pandaboard"
DISTRO= "poky"
DISTRO_VERSION= "1.2+snapshot-20120730"
TUNE_FEATURES = "armv7a vfp neon cortexa9"
TARGET_FPU= "vfp-neon"
meta
meta-yocto= "master:7411158e1f980cd71c432026fa2f68ab80e3541e"
meta-oe = "master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb"
meta-ti = "master:9bc77dff5f84578e259f8225bfa0656d94a2a60a"
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
BBMASK by itself didn't solve my particular problem. I'll try the other
suggestions and report back.
What other problem do you have? That BBMASK should keep bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that mask...
When I just used the statement:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
I got the same error as my original post.
The only way you could get that same error is if you already have a BBMASK
statement somewhere and this one is being ignored because of the ?= assignment.
So I started with a clean build again. This time I only added the BBMASK
statement you suggested. I got the following error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by your yocto build.
Thanks, that makes more sense now. I removed the layer meta-systemd from
bblayers.conf and used the
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on meta-systemd
are there, but the mask removes that?? Why can you remove a dependency?
The dependency on systemd comes from this recipe:
meta-ti/recipes-misc/payload/bonescript.bb
The BBMASK is making bitbake ignore that recipe (you don't need it), hence no
dependency.
I got core-image-minimal built without errors, Thanks, now I need to ask some
questions about booting that image. I'm assuming that I can follow the
instructions on pandaboard.org
for creating the SD card format and just copy the deploy/image/ u-boot, MLO,
uImage, and rootfs to the right places and boot the sdcard in the pandaboard.
Anyway, that's what I
tried. I'm connected to the panadboard via serial port and the U-Boot works
and the uImage seems to be found, but I don't get a login console on the serial
port:
U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03)
Texas Instruments OMAP4430 ES2.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03)
CPU : OMAP4430 ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
In:serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
4176404 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4176340 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Start with the obvious - check the bootparams in U-Boot. Break into
the boot process and run the 'printenv' comm
[yocto] what's the state of building for a (OMAP4460) pandaboard ES?
i notice that the current meta-ti layer has a pandaboard.conf file that refers specifically to the OMAP 4430 -- the original panda. this weekend, i'd like to build, say, a core-image-minimal for my ES. is there a writeup anywhere that documents what issues i might run into regarding the panda versus the panda ES? thanks. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/31/2012 07:25 AM, Gary Thomas wrote:
On 2012-07-30 13:11, Gary Thomas wrote:
On 2012-07-30 12:49, Jim Abernathy wrote:
On 07/30/2012 01:16 PM, Gary Thomas wrote:
On 2012-07-30 11:09, Jim Abernathy wrote:
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal
for the machine "pandaboard". Besides the basics, I put in
a license statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time
build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "5"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
"
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5:
Could not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= "1.15.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "pandaboard"
DISTRO= "poky"
DISTRO_VERSION= "1.2+snapshot-20120730"
TUNE_FEATURES = "armv7a vfp neon cortexa9"
TARGET_FPU= "vfp-neon"
meta
meta-yocto=
"master:7411158e1f980cd71c432026fa2f68ab80e3541e"
meta-oe =
"master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb"
meta-ti =
"master:9bc77dff5f84578e259f8225bfa0656d94a2a60a"
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
BBMASK by itself didn't solve my particular problem. I'll
try the other suggestions and report back.
What other problem do you have? That BBMASK should keep
bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that
mask...
When I just used the statement:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
I got the same error as my original post.
The only way you could get that same error is if you already
have a BBMASK
statement somewhere and this one is being ignored because of
the ?= assignment.
So I started with a clean build again. This time I only added
the BBMASK statement you suggested. I got the following error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by your
yocto build.
Thanks, that makes more sense now. I removed the layer
meta-systemd from bblayers.conf and used the
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on
meta-systemd are there, but the mask removes that?? Why can you
remove a dependency?
The dependency on systemd comes from this recipe:
meta-ti/recipes-misc/payload/bonescript.bb
The BBMASK is making bitbake ignore that recipe (you don't need
it), hence no dependency.
I got core-image-minimal built without errors, Thanks, now I need to
ask some questions about booting that image. I'm assuming that I
can follow the instructions on pandaboard.org
for creating the SD card format and just copy the deploy/image/
u-boot, MLO, uImage, and rootfs to the right places and boot the
sdcard in the pandaboard. Anyway, that's what I
tried. I'm connected to the panadboard via serial port and the
U-Boot works and the uImage seems to be found, but I don't get a
login console on the serial port:
U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03)
Texas Instruments OMAP4430 ES2.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03)
CPU : OMAP4430 ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
In:serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
4176404 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4176340 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Start with the obvious - check the bootparams
Re: [yocto] build error pandaboard on master
On Tue, Jul 31, 2012 at 07:47:34AM -0400, Jim Abernathy wrote:
> On 07/31/2012 07:25 AM, Gary Thomas wrote:
> > On 2012-07-30 13:11, Gary Thomas wrote:
> >> On 2012-07-30 12:49, Jim Abernathy wrote:
> >>> On 07/30/2012 01:16 PM, Gary Thomas wrote:
> On 2012-07-30 11:09, Jim Abernathy wrote:
> > On 07/30/2012 12:57 PM, Gary Thomas wrote:
> >> On 2012-07-30 10:50, Jim Abernathy wrote:
> >>> On 07/30/2012 10:21 AM, Gary Thomas wrote:
> On 2012-07-30 08:11, Jim Abernathy wrote:
> > On 07/30/2012 09:56 AM, Gary Thomas wrote:
> >> On 2012-07-30 07:48, Jim Abernathy wrote:
> >>> On 07/30/2012 09:15 AM, Gary Thomas wrote:
> On 2012-07-30 06:53, Jim Abernathy wrote:
> > I'm on master branch trying to build core-image-minimal
> > for the machine "pandaboard". Besides the basics, I put in
> > a license statement for cloud9 into local.conf.
> >
> > My bblayer.conf is as follows:
> >
> > # LAYER_CONF_VERSION is increased each time
> > build/conf/bblayers.conf
> > # changes incompatibly
> > LCONF_VERSION = "5"
> >
> > BBPATH = "${TOPDIR}"
> > BBFILES ?= ""
> >
> > BBLAYERS ?= " \
> >/home/jim/poky/meta \
> >/home/jim/poky/meta-yocto \
> >/home/jim/meta-openembedded/meta-oe \
> >/home/jim/meta-ti \
> >"
> >
> > The error I'm getting is:
> >
> > ERROR: ParseError at
> > /home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5:
> > Could not inherit file classes/systemd.bbclass
> >
> > Build Configuration:
> > BB_VERSION= "1.15.3"
> > TARGET_ARCH = "arm"
> > TARGET_OS = "linux-gnueabi"
> > MACHINE = "pandaboard"
> > DISTRO= "poky"
> > DISTRO_VERSION= "1.2+snapshot-20120730"
> > TUNE_FEATURES = "armv7a vfp neon cortexa9"
> > TARGET_FPU= "vfp-neon"
> > meta
> > meta-yocto=
> > "master:7411158e1f980cd71c432026fa2f68ab80e3541e"
> > meta-oe =
> > "master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb"
> > meta-ti =
> > "master:9bc77dff5f84578e259f8225bfa0656d94a2a60a"
> >
> > ERROR: Nothing PROVIDES 'pseudo-native'
>
> Try adding this in local.conf:
> BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
>
> >>> BBMASK by itself didn't solve my particular problem. I'll
> >>> try the other suggestions and report back.
> >>
> >> What other problem do you have? That BBMASK should keep
> >> bitbake from
> >> trying to parse the recipe mentioned above.
> >>
> >> Note: I use these layers with Yocto all the time with that
> >> mask...
> >>
> >
> > When I just used the statement:
> >
> > BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
> >
> > I got the same error as my original post.
>
> The only way you could get that same error is if you already
> have a BBMASK
> statement somewhere and this one is being ignored because of
> the ?= assignment.
>
> >>> So I started with a clean build again. This time I only added
> >>> the BBMASK statement you suggested. I got the following error:
> >>>
> >>> ERROR: No recipes available for:
> >>> /home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
> >>>
> >>>
> >>> /home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
> >>>
> >>>
> >>> ERROR: Command execution failed: Exited with 1
> >>>
> >>> I'm guessing the BBMASK needs to call out
> >>> meta-openembedded/meta-systemd/meta-gnome and meta-efl?
> >>
> >> Or don't include those layers - meta-systemd isn't needed by your
> >> yocto build.
> >>
> > Thanks, that makes more sense now. I removed the layer
> > meta-systemd from bblayers.conf and used the
> >
> > BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
> >
> > statement in local.conf to solves the problem.
> >
> > What is really causing the problem? Without it dependencies on
> > meta-systemd are there, but the mask removes that?? Why can you
> > remove a dependency?
>
> The dependency on systemd comes from this recipe:
> meta-ti/recipes-misc/payload/bonescript.bb
> The BBMASK is making bitbake ignore that recipe (you don't need
> it),
Re: [yocto] build error pandaboard on master
On 2012-07-31 05:49, Martin Jansa wrote:
On Tue, Jul 31, 2012 at 07:47:34AM -0400, Jim Abernathy wrote:
On 07/31/2012 07:25 AM, Gary Thomas wrote:
On 2012-07-30 13:11, Gary Thomas wrote:
On 2012-07-30 12:49, Jim Abernathy wrote:
On 07/30/2012 01:16 PM, Gary Thomas wrote:
On 2012-07-30 11:09, Jim Abernathy wrote:
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal
for the machine "pandaboard". Besides the basics, I put in
a license statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time
build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "5"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
"
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5:
Could not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= "1.15.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "pandaboard"
DISTRO= "poky"
DISTRO_VERSION= "1.2+snapshot-20120730"
TUNE_FEATURES = "armv7a vfp neon cortexa9"
TARGET_FPU= "vfp-neon"
meta
meta-yocto=
"master:7411158e1f980cd71c432026fa2f68ab80e3541e"
meta-oe =
"master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb"
meta-ti =
"master:9bc77dff5f84578e259f8225bfa0656d94a2a60a"
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
BBMASK by itself didn't solve my particular problem. I'll
try the other suggestions and report back.
What other problem do you have? That BBMASK should keep
bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that
mask...
When I just used the statement:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
I got the same error as my original post.
The only way you could get that same error is if you already
have a BBMASK
statement somewhere and this one is being ignored because of
the ?= assignment.
So I started with a clean build again. This time I only added
the BBMASK statement you suggested. I got the following error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by your
yocto build.
Thanks, that makes more sense now. I removed the layer
meta-systemd from bblayers.conf and used the
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on
meta-systemd are there, but the mask removes that?? Why can you
remove a dependency?
The dependency on systemd comes from this recipe:
meta-ti/recipes-misc/payload/bonescript.bb
The BBMASK is making bitbake ignore that recipe (you don't need
it), hence no dependency.
I got core-image-minimal built without errors, Thanks, now I need to
ask some questions about booting that image. I'm assuming that I
can follow the instructions on pandaboard.org
for creating the SD card format and just copy the deploy/image/
u-boot, MLO, uImage, and rootfs to the right places and boot the
sdcard in the pandaboard. Anyway, that's what I
tried. I'm connected to the panadboard via serial port and the
U-Boot works and the uImage seems to be found, but I don't get a
login console on the serial port:
U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03)
Texas Instruments OMAP4430 ES2.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03)
CPU : OMAP4430 ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
In:serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
4176404 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4176340 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing L
[yocto] [PATCH] Changed ownership of linux-libc-headers[-yocto]
Changing the owner to Bruce Ashfield, as agreed. Signed-off-by: Bogdan Marinescu --- meta-yocto/conf/distro/include/maintainers.inc |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-yocto/conf/distro/include/maintainers.inc b/meta-yocto/conf/distro/include/maintainers.inc index 0f34d64..07fadb6 100644 --- a/meta-yocto/conf/distro/include/maintainers.inc +++ b/meta-yocto/conf/distro/include/maintainers.inc @@ -407,8 +407,8 @@ RECIPE_MAINTAINER_pn-libxxf86vm = "Valentin Popa " RECIPE_MAINTAINER_pn-libzypp = "Mark Hatle " RECIPE_MAINTAINER_pn-lighttpd = "Valentin Popa " RECIPE_MAINTAINER_pn-linux-firmware = "Cristian Iorga " -RECIPE_MAINTAINER_pn-linux-libc-headers = "Bogdan Marinescu " -RECIPE_MAINTAINER_pn-linux-libc-headers-yocto = "Bogdan Marinescu " +RECIPE_MAINTAINER_pn-linux-libc-headers = "Bruce Ashfield " +RECIPE_MAINTAINER_pn-linux-libc-headers-yocto = "Bruce Ashfield " RECIPE_MAINTAINER_pn-linux-yocto = "Darren Hart " RECIPE_MAINTAINER_pn-linux-yocto-rt = "Darren Hart " RECIPE_MAINTAINER_pn-linuxdoc-tools = "Scott Garman " -- 1.7.9.5 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/31/2012 07:53 AM, Gary Thomas wrote:
On 2012-07-31 05:49, Martin Jansa wrote:
On Tue, Jul 31, 2012 at 07:47:34AM -0400, Jim Abernathy wrote:
On 07/31/2012 07:25 AM, Gary Thomas wrote:
On 2012-07-30 13:11, Gary Thomas wrote:
On 2012-07-30 12:49, Jim Abernathy wrote:
On 07/30/2012 01:16 PM, Gary Thomas wrote:
On 2012-07-30 11:09, Jim Abernathy wrote:
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal
for the machine "pandaboard". Besides the basics, I put in
a license statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time
build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "5"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
"
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5:
Could not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= "1.15.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "pandaboard"
DISTRO= "poky"
DISTRO_VERSION= "1.2+snapshot-20120730"
TUNE_FEATURES = "armv7a vfp neon cortexa9"
TARGET_FPU= "vfp-neon"
meta
meta-yocto=
"master:7411158e1f980cd71c432026fa2f68ab80e3541e"
meta-oe =
"master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb"
meta-ti =
"master:9bc77dff5f84578e259f8225bfa0656d94a2a60a"
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
BBMASK by itself didn't solve my particular problem. I'll
try the other suggestions and report back.
What other problem do you have? That BBMASK should keep
bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that
mask...
When I just used the statement:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
I got the same error as my original post.
The only way you could get that same error is if you already
have a BBMASK
statement somewhere and this one is being ignored because of
the ?= assignment.
So I started with a clean build again. This time I only added
the BBMASK statement you suggested. I got the following error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by your
yocto build.
Thanks, that makes more sense now. I removed the layer
meta-systemd from bblayers.conf and used the
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on
meta-systemd are there, but the mask removes that?? Why can you
remove a dependency?
The dependency on systemd comes from this recipe:
meta-ti/recipes-misc/payload/bonescript.bb
The BBMASK is making bitbake ignore that recipe (you don't need
it), hence no dependency.
I got core-image-minimal built without errors, Thanks, now I need to
ask some questions about booting that image. I'm assuming that I
can follow the instructions on pandaboard.org
for creating the SD card format and just copy the deploy/image/
u-boot, MLO, uImage, and rootfs to the right places and boot the
sdcard in the pandaboard. Anyway, that's what I
tried. I'm connected to the panadboard via serial port and the
U-Boot works and the uImage seems to be found, but I don't get a
login console on the serial port:
U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03)
Texas Instruments OMAP4430 ES2.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03)
CPU : OMAP4430 ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
In:serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
4176404 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4176340 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ..
Re: [yocto] build error pandaboard on master
On 2012-07-31 06:00, Jim Abernathy wrote:
On 07/31/2012 07:53 AM, Gary Thomas wrote:
On 2012-07-31 05:49, Martin Jansa wrote:
On Tue, Jul 31, 2012 at 07:47:34AM -0400, Jim Abernathy wrote:
On 07/31/2012 07:25 AM, Gary Thomas wrote:
On 2012-07-30 13:11, Gary Thomas wrote:
On 2012-07-30 12:49, Jim Abernathy wrote:
On 07/30/2012 01:16 PM, Gary Thomas wrote:
On 2012-07-30 11:09, Jim Abernathy wrote:
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal
for the machine "pandaboard". Besides the basics, I put in
a license statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time
build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "5"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
"
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5:
Could not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= "1.15.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "pandaboard"
DISTRO= "poky"
DISTRO_VERSION= "1.2+snapshot-20120730"
TUNE_FEATURES = "armv7a vfp neon cortexa9"
TARGET_FPU= "vfp-neon"
meta
meta-yocto=
"master:7411158e1f980cd71c432026fa2f68ab80e3541e"
meta-oe =
"master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb"
meta-ti =
"master:9bc77dff5f84578e259f8225bfa0656d94a2a60a"
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
BBMASK by itself didn't solve my particular problem. I'll
try the other suggestions and report back.
What other problem do you have? That BBMASK should keep
bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that
mask...
When I just used the statement:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
I got the same error as my original post.
The only way you could get that same error is if you already
have a BBMASK
statement somewhere and this one is being ignored because of
the ?= assignment.
So I started with a clean build again. This time I only added
the BBMASK statement you suggested. I got the following error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by your
yocto build.
Thanks, that makes more sense now. I removed the layer
meta-systemd from bblayers.conf and used the
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on
meta-systemd are there, but the mask removes that?? Why can you
remove a dependency?
The dependency on systemd comes from this recipe:
meta-ti/recipes-misc/payload/bonescript.bb
The BBMASK is making bitbake ignore that recipe (you don't need
it), hence no dependency.
I got core-image-minimal built without errors, Thanks, now I need to
ask some questions about booting that image. I'm assuming that I
can follow the instructions on pandaboard.org
for creating the SD card format and just copy the deploy/image/
u-boot, MLO, uImage, and rootfs to the right places and boot the
sdcard in the pandaboard. Anyway, that's what I
tried. I'm connected to the panadboard via serial port and the
U-Boot works and the uImage seems to be found, but I don't get a
login console on the serial port:
U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03)
Texas Instruments OMAP4430 ES2.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03)
CPU : OMAP4430 ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
In:serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
4176404 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4176340 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksu
Re: [yocto] build error pandaboard on master
On 07/31/2012 08:14 AM, Gary Thomas wrote:
On 2012-07-31 06:00, Jim Abernathy wrote:
On 07/31/2012 07:53 AM, Gary Thomas wrote:
On 2012-07-31 05:49, Martin Jansa wrote:
On Tue, Jul 31, 2012 at 07:47:34AM -0400, Jim Abernathy wrote:
On 07/31/2012 07:25 AM, Gary Thomas wrote:
On 2012-07-30 13:11, Gary Thomas wrote:
On 2012-07-30 12:49, Jim Abernathy wrote:
On 07/30/2012 01:16 PM, Gary Thomas wrote:
On 2012-07-30 11:09, Jim Abernathy wrote:
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal
for the machine "pandaboard". Besides the basics, I
put in
a license statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time
build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "5"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
"
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5:
Could not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION= "1.15.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "pandaboard"
DISTRO= "poky"
DISTRO_VERSION= "1.2+snapshot-20120730"
TUNE_FEATURES = "armv7a vfp neon cortexa9"
TARGET_FPU= "vfp-neon"
meta
meta-yocto=
"master:7411158e1f980cd71c432026fa2f68ab80e3541e"
meta-oe =
"master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb"
meta-ti =
"master:9bc77dff5f84578e259f8225bfa0656d94a2a60a"
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
BBMASK by itself didn't solve my particular problem. I'll
try the other suggestions and report back.
What other problem do you have? That BBMASK should keep
bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that
mask...
When I just used the statement:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
I got the same error as my original post.
The only way you could get that same error is if you already
have a BBMASK
statement somewhere and this one is being ignored because of
the ?= assignment.
So I started with a clean build again. This time I only added
the BBMASK statement you suggested. I got the following
error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by
your
yocto build.
Thanks, that makes more sense now. I removed the layer
meta-systemd from bblayers.conf and used the
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on
meta-systemd are there, but the mask removes that?? Why can you
remove a dependency?
The dependency on systemd comes from this recipe:
meta-ti/recipes-misc/payload/bonescript.bb
The BBMASK is making bitbake ignore that recipe (you don't need
it), hence no dependency.
I got core-image-minimal built without errors, Thanks, now I
need to
ask some questions about booting that image. I'm assuming that I
can follow the instructions on pandaboard.org
for creating the SD card format and just copy the deploy/image/
u-boot, MLO, uImage, and rootfs to the right places and boot the
sdcard in the pandaboard. Anyway, that's what I
tried. I'm connected to the panadboard via serial port and the
U-Boot works and the uImage seems to be found, but I don't get a
login console on the serial port:
U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03)
Texas Instruments OMAP4430 ES2.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03)
CPU : OMAP4430 ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
In:serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
4176404 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:4176340 Bytes = 4 MiB
Load Address: 80
Re: [yocto] what's the state of building for a (OMAP4460) pandaboard ES?
On Tuesday 31 July 2012 06:43:17 Robert P. J. Day wrote: > i notice that the current meta-ti layer has a pandaboard.conf file > that refers specifically to the OMAP 4430 -- the original panda. > this weekend, i'd like to build, say, a core-image-minimal for my ES. > is there a writeup anywhere that documents what issues i might run > into regarding the panda versus the panda ES? thanks. I'm not sure but I think you probably need to direct this question to the meta-ti mailing list. https://lists.yoctoproject.org/listinfo/meta-ti Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] what's the state of building for a (OMAP4460) pandaboard ES?
On 07/31/2012 11:06 AM, Paul Eggleton wrote: On Tuesday 31 July 2012 06:43:17 Robert P. J. Day wrote: i notice that the current meta-ti layer has a pandaboard.conf file that refers specifically to the OMAP 4430 -- the original panda. this weekend, i'd like to build, say, a core-image-minimal for my ES. is there a writeup anywhere that documents what issues i might run into regarding the panda versus the panda ES? thanks. I'm not sure but I think you probably need to direct this question to the meta-ti mailing list. https://lists.yoctoproject.org/listinfo/meta-ti I did see this question, I just don't have an answer. We are seeing if we can get a part time maintainer for panda lined up. Right now it is just something a few volunteers did a few months ago. There are no product level plans for panda and Yocto. I hope to get panda on the list of platforms for nightly (or at least weekly) builds. That way the status will be visible. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [RFC 0/3] Cheat sheet for hello world project
Hi Atanas, This patch set looks nice, couple comments: 1. Is it just meant for C++ project since it's applicable to C project as well 2. I'd think this should be targeted for the upcoming 1.3 release that's targeted for Oct.. For 1.3 release we are based on the latest Juno release and also, there's a new feature added for SDK which makes it rellocatable which is under patch review atm. I'd suggest you follow bug 2383 once it's marked resolved, which means the patch is merged into master. Then pull down the latest master and the latest Eclipse plug-in to capture the latest behavior and update the cheatsheet contents accordingly. Thanks, Jessica -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Atanas Gegov Sent: Tuesday, July 24, 2012 8:54 AM To: yocto@yoctoproject.org Subject: [yocto] [RFC 0/3] Cheat sheet for hello world project From: Atanas Gegov Hi, currently the adt manual contains a description of how to create a new project (chapter 4.2). Also some videos are explaining how to achieve this. Eclipse provides a nice way of interactive tutorials with the cheat sheets and I thought it would be nice to have this kind of user help. So I have created a cheat sheet for the 'Hello World C++ Autotools Project' project delivered with the yocto ide. It guides the user through the process of creating and building the hello world project. Some operations such as changing to the C/C++ perspective can even be automated helping the user to get started with the project. Cheers, Atanas Atanas Gegov (3): plugins/sdk.ide.doc.user: Added plugin for ide specific user help feature/sdk: Added user doc plugin plugins/sdk.ide.doc.user: Added cheat sheet for hello world project features/org.yocto.sdk/feature.xml |8 + plugins/org.yocto.sdk.ide.doc.user/.classpath |6 + plugins/org.yocto.sdk.ide.doc.user/.project| 28 +++ .../.settings/org.eclipse.jdt.core.prefs |8 + .../META-INF/MANIFEST.MF |8 + .../OSGI-INF/l10n/bundle.properties|7 + .../org.yocto.sdk.ide.doc.user/build.properties|6 + .../cheatsheets/createNewHelloWorldProject.xml | 187 plugins/org.yocto.sdk.ide.doc.user/plugin.xml | 13 ++ 9 files changed, 271 insertions(+), 0 deletions(-) create mode 100644 plugins/org.yocto.sdk.ide.doc.user/.classpath create mode 100644 plugins/org.yocto.sdk.ide.doc.user/.project create mode 100644 plugins/org.yocto.sdk.ide.doc.user/.settings/org.eclipse.jdt.core.prefs create mode 100644 plugins/org.yocto.sdk.ide.doc.user/META-INF/MANIFEST.MF create mode 100644 plugins/org.yocto.sdk.ide.doc.user/OSGI-INF/l10n/bundle.properties create mode 100644 plugins/org.yocto.sdk.ide.doc.user/build.properties create mode 100644 plugins/org.yocto.sdk.ide.doc.user/cheatsheets/createNewHelloWorldProject.xml create mode 100644 plugins/org.yocto.sdk.ide.doc.user/plugin.xml -- 1.7.5.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 07/31/2012 09:33 AM, Jim Abernathy wrote:
On 07/31/2012 08:14 AM, Gary Thomas wrote:
On 2012-07-31 06:00, Jim Abernathy wrote:
On 07/31/2012 07:53 AM, Gary Thomas wrote:
On 2012-07-31 05:49, Martin Jansa wrote:
On Tue, Jul 31, 2012 at 07:47:34AM -0400, Jim Abernathy wrote:
On 07/31/2012 07:25 AM, Gary Thomas wrote:
On 2012-07-30 13:11, Gary Thomas wrote:
On 2012-07-30 12:49, Jim Abernathy wrote:
On 07/30/2012 01:16 PM, Gary Thomas wrote:
On 2012-07-30 11:09, Jim Abernathy wrote:
On 07/30/2012 12:57 PM, Gary Thomas wrote:
On 2012-07-30 10:50, Jim Abernathy wrote:
On 07/30/2012 10:21 AM, Gary Thomas wrote:
On 2012-07-30 08:11, Jim Abernathy wrote:
On 07/30/2012 09:56 AM, Gary Thomas wrote:
On 2012-07-30 07:48, Jim Abernathy wrote:
On 07/30/2012 09:15 AM, Gary Thomas wrote:
On 2012-07-30 06:53, Jim Abernathy wrote:
I'm on master branch trying to build core-image-minimal
for the machine "pandaboard". Besides the basics, I
put in
a license statement for cloud9 into local.conf.
My bblayer.conf is as follows:
# LAYER_CONF_VERSION is increased each time
build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "5"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/jim/poky/meta \
/home/jim/poky/meta-yocto \
/home/jim/meta-openembedded/meta-oe \
/home/jim/meta-ti \
"
The error I'm getting is:
ERROR: ParseError at
/home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5:
Could not inherit file classes/systemd.bbclass
Build Configuration:
BB_VERSION = "1.15.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "pandaboard"
DISTRO = "poky"
DISTRO_VERSION = "1.2+snapshot-20120730"
TUNE_FEATURES = "armv7a vfp neon cortexa9"
TARGET_FPU = "vfp-neon"
meta
meta-yocto =
"master:7411158e1f980cd71c432026fa2f68ab80e3541e"
meta-oe =
"master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb"
meta-ti =
"master:9bc77dff5f84578e259f8225bfa0656d94a2a60a"
ERROR: Nothing PROVIDES 'pseudo-native'
Try adding this in local.conf:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
BBMASK by itself didn't solve my particular problem. I'll
try the other suggestions and report back.
What other problem do you have? That BBMASK should keep
bitbake from
trying to parse the recipe mentioned above.
Note: I use these layers with Yocto all the time with that
mask...
When I just used the statement:
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
I got the same error as my original post.
The only way you could get that same error is if you already
have a BBMASK
statement somewhere and this one is being ignored because of
the ?= assignment.
So I started with a clean build again. This time I only added
the BBMASK statement you suggested. I got the following error:
ERROR: No recipes available for:
/home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
/home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
ERROR: Command execution failed: Exited with 1
I'm guessing the BBMASK needs to call out
meta-openembedded/meta-systemd/meta-gnome and meta-efl?
Or don't include those layers - meta-systemd isn't needed by
your
yocto build.
Thanks, that makes more sense now. I removed the layer
meta-systemd from bblayers.conf and used the
BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
statement in local.conf to solves the problem.
What is really causing the problem? Without it dependencies on
meta-systemd are there, but the mask removes that?? Why can you
remove a dependency?
The dependency on systemd comes from this recipe:
meta-ti/recipes-misc/payload/bonescript.bb
The BBMASK is making bitbake ignore that recipe (you don't need
it), hence no dependency.
I got core-image-minimal built without errors, Thanks, now I
need to
ask some questions about booting that image. I'm assuming that I
can follow the instructions on pandaboard.org
for creating the SD card format and just copy the deploy/image/
u-boot, MLO, uImage, and rootfs to the right places and boot the
sdcard in the pandaboard. Anyway, that's what I
tried. I'm connected to the panadboard via serial port and the
U-Boot works and the uImage seems to be found, but I don't get a
login console on the serial port:
U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03)
Texas Instruments OMAP4430 ES2.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03)
CPU : OMAP4430 ES2.1
Board: OMAP4 Panda
I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
4176404 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-3.1.0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4176340 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Unco
[yocto] Unable to get serial console login prompt - PowerPC 440 Virtex 5 processor
Hi, I am unable to get a serial console login prompt using yocto generate rootfilesystem (core-image-minimal), for a PowerPC 440 target. I saw on another thread that even for the pandaboard, a similar situation exists: > On 2012-07-30 13:11, Gary Thomas wrote: >> On 2012-07-30 12:49, Jim Abernathy wrote: >>> On 07/30/2012 01:16 PM, Gary Thomas wrote: >>> I got core-image-minimal built without errors, Thanks, now I need to ask >>> some questions about booting that image. I'm assuming that I can follow >>> the instructions on pandaboard.org >>> for creating the SD card format and just copy the deploy/image/ u-boot, >>> MLO, uImage, and rootfs to the right places and boot the sdcard in the >>> pandaboard. Anyway, that's what I >>> tried. I'm connected to the panadboard via serial port and the U-Boot >>> works and the uImage seems to be found, but I don't get a login console on >>> the serial port: >>> >>> U-Boot SPL 2011.12-dirty (Jul 30 2012 - 13:44:03) >>> Texas Instruments OMAP4430 ES2.1 >>> OMAP SD/MMC: 0 >>> reading u-boot.img >>> reading u-boot.img >>> >>> >>> U-Boot 2011.12-dirty (Jul 30 2012 - 13:44:03) >>> >>> CPU : OMAP4430 ES2.1 >>> Board: OMAP4 Panda >>> I2C: ready >>> DRAM: 1 GiB >>> MMC: OMAP SD/MMC: 0 >>> Using default environment >>> >>> In:serial >>> Out: serial >>> Err: serial >>> Hit any key to stop autoboot: 0 >>> reading boot.scr >>> >>> ** Unable to read "boot.scr" from mmc 0:1 ** >>> reading uImage >>> >>> 4176404 bytes read >>> Booting from mmc0 ... >>> ## Booting kernel from Legacy Image at 8200 ... >>>Image Name: Linux-3.1.0 >>>Image Type: ARM Linux Kernel Image (uncompressed) >>>Data Size:4176340 Bytes = 4 MiB >>>Load Address: 80008000 >>>Entry Point: 80008000 >>>Verifying Checksum ... OK >>>Loading Kernel Image ... OK >>> OK >>> >>> Starting kernel ... >>> >>> Uncompressing Linux... done, booting the kernel. >> >> Start with the obvious - check the bootparams in U-Boot. Break into >> the boot process and run the 'printenv' command. What's the value of >> the "console" variable? >> >> n.b. I've not tried this exact setup on the PandaBoard. I may have time >> later today to do so. >> > > I've just verified that this does fail when using yocto:master I'm pretty > sure that the problem is related to the use of GCC 4.7.1 - I've had similar > problems with ARM kernels & GCC 4.7.1 in the past. Can someone confirm? Any suggestions on how to get past this issue? Is serial console login prompt broken on yocto for targets other than Intel? Does it work on ARM or PowerPC at the moment, with the latest yocto updates as of today? My /etc/inittab looks like this: S:2345:respawn:/sbin/getty 9600 ttyS0 Here is the output of my kernel boot screen: zImage starting: loaded at 0x0080 (sp: 0x00d71fb0) Allocating 0x4cea6c bytes for kernel ... gunzipping (0x <- 0x0080f000:0x009ddcf9)...done 0x3b15c0 bytes Attached initrd image at 0x009de000-0x00d7088a initrd head: 0x1f8b0808 Linux/PowerPC load: console=ttyS0 ip=off root=/dev/ram rw Finalizing device tree... flat tree at 0xd7e0e0 [0.00] Using Xilinx Virtex440 machine description [0.00] Linux version 3.3.0-14.2-build1+ (elvis@eos) (gcc version 4.7.2 20120706 (prerelease) (GCC) ) #37 PREEMPT Tue Jul 31 21:12:34 GST 2012 [0.00] Found initrd at 0xc09de000:0xc0d7088a [0.00] Zone PFN ranges: [0.00] DMA 0x -> 0x0001 [0.00] Normal empty [0.00] Movable zone start PFN for each node [0.00] Early memory PFN ranges [0.00] 0: 0x -> 0x0001 [0.00] MMU: Allocated 1088 bytes of context maps for 255 contexts [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [0.00] Kernel command line: console=ttyS0 ip=off root=/dev/ram rw [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Memory: 251200k/262144k available (3596k kernel code, 10944k reserved, 188k data, 1138k bss, 148k init) [0.00] Kernel virtual memory layout: [0.00] * 0xfffdf000..0xf000 : fixmap [0.00] * 0xfde0..0xfe00 : consistent mem [0.00] * 0xfde0..0xfde0 : early ioremap [0.00] * 0xd100..0xfde0 : vmalloc & ioremap [0.00] NR_IRQS:512 [0.00] clocksource: timebase mult[280] shift[24] registered [0.00] Console: colour dummy device 80x25 [0.000455] pid_max: default: 32768 minimum: 301 [0.000815] Mount-cache hash table entries: 512 [0.008275] NET: Registered protocol family 16 [0.014106] PCI: Probing PCI hardware [0.041141] bio: cre
[yocto] [for denzil] kernel.bbclass: Copy bounds.h only if it exists, needed for 2.6.x.
From: Leon Woestenberg
Linux 2.6.x kernels did not (all) have the bounds.h file, so copy
only iff exists.
(See OE-Core 02ac0d1b65389e1779d5f95047f761d7a82ef7a4)
Signed-off-by: Leon Woestenberg
---
meta/classes/kernel.bbclass |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index c21ab96..5f6ff66 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -183,6 +183,11 @@ kernel_do_install() {
cp arch/powerpc/lib/crtsavres.o
$kerneldir/arch/powerpc/lib/crtsavres.o
fi
+ # Necessary for building modules like compat-wireless.
+ if [ -f include/generated/bounds.h ]; then
+ cp include/generated/bounds.h
$kerneldir/include/generated/bounds.h
+ fi
+
# Remove the following binaries which cause strip errors
# during do_package for cross-compiled platforms
bin_files="arch/powerpc/boot/addnote arch/powerpc/boot/hack-coff \
--
1.7.0.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [for denzil] kernel.bbclass: Copy bounds.h only if it exists, needed for 2.6.x.
On 07/31/2012 01:35 PM, sidebranch.openembed...@gmail.com wrote:
From: Leon Woestenberg
Linux 2.6.x kernels did not (all) have the bounds.h file, so copy
only iff exists.
(See OE-Core 02ac0d1b65389e1779d5f95047f761d7a82ef7a4)
Signed-off-by: Leon Woestenberg
---
meta/classes/kernel.bbclass |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index c21ab96..5f6ff66 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -183,6 +183,11 @@ kernel_do_install() {
cp arch/powerpc/lib/crtsavres.o
$kerneldir/arch/powerpc/lib/crtsavres.o
fi
+ # Necessary for building modules like compat-wireless.
+ if [ -f include/generated/bounds.h ]; then
+ cp include/generated/bounds.h
$kerneldir/include/generated/bounds.h
+ fi
+
# Remove the following binaries which cause strip errors
# during do_package for cross-compiled platforms
bin_files="arch/powerpc/boot/addnote arch/powerpc/boot/hack-coff \
Merged into my sgarman/denzil-next branches:
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next
If this passes a round of autobuilder tests, I'll be submitting a pull
request to the official denzil branch shortly thereafter.
Thanks,
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [for denzil] kernel.bbclass: Copy bounds.h only if it exists, needed for 2.6.x.
On Wed, Aug 1, 2012 at 12:00 AM, Scott Garman wrote: > On 07/31/2012 01:35 PM, sidebranch.openembed...@gmail.com wrote: > >> From: Leon Woestenberg >> >> Linux 2.6.x kernels did not (all) have the bounds.h file, so copy >> only iff exists.Merged into my sgarman/denzil-next branches: >> > > > http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next > > http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=sgarman/denzil-next > > If this passes a round of autobuilder tests, I'll be submitting a pull > request to the official denzil branch shortly thereafter. > Thanks, > Scott > > Thanks Scott. Also thanks for the pointers to denzil-next. I will consider adding those to my build rounds locally also. Regards, Leon. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, July 31, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada)
Attendees: Dave, LaurentiuP, LaurentiuS, Alex, Mark, Nitin, Beth, Paul, MichaelH, Kevin, Tom, Jessica, Richard, Darren, Bruce, Jefro, Ross, JeffP, ChrisL, Bjorn, Song Agenda: * Opens collection - 5 min (Song) * Yocto 1.3 status - 10 min (Song/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status - Reminder to the team: feature freeze for M3 is coming up this Sunday night (US time). Please get your features in asap and allow some patch review and rework time. - Bug trend is still going up. We got more open medium+ bugs. Please focus more on bug fixing. - P1+high item review: . 2038/BogdanM: at risk, maybe delayed to M4 . 1649/Bruce: on track. . 2396/Bruce: LTSI integration. The LTSI release may not be out until the end of this year. We are forming up a plan now. Expect to announce in the upcoming LinuxCon on our plan. . 2165/Cristian: working on it, on track. . 1621/LaurentiuP: working on this. Will try to get it in for M3. . 1991/anliming: 80% done. Song is following up with Shane/Liming on this. . 2614/Paul: on track. . 1179/Richard: On track. Will pull patches together this week. . 1369/BogdanM: at risk, may need to move to M4. . 61/LaurentiuP: at risk, may need to move to M4. . 2010/MichaelH: at risk. Need another 2 weeks after the 2 new AB machines online. Need to move to M4. . 2420/Paul: Original problems have been fixed. Will close this bug and open new ones to track progress on other related issues. New ones won't be high. . 2775/PaulG,Darren: MPC BSP has been fixed. Waiting for a patch merge in kernel. Will close this one if the patch merges. If not, then close this one and open new bugs to track remaining issues. . 2319/RossB: will look at it tomorrow. Song will follow up. . 2162/Valentin: at risk, may be moved to M4. - RP/Master status: a number of changes coming in. various people on vacation, limited resource. Master is not stable, it's being worked on, will stabilize as soon as we can. May slow down the rate of changes going in. Complicated by the 2 new autobuilder machines, related to sstate changes. * SWAT team rotation: Nitin -> Beth * Opens - 10 min Nitin: SWAT team rotation. Covered. * Team sharing - 20 min - Mark: refactoring image creation deployment mechanism. Will send email today on the solution. Appreciate if people can comment. Sent to Richard and Darren first. RP: it seems like a rewrite. Mark: The intent is not to rewrite. We want to change something, would like to do it step by step. It does not have to be done in 1.3. Darren: we do have a bug open for image creation. Dave: We have done related work (PaulE). Mark: what we have for 1.3 is good enough, this is the next step. RP: try to improve the code legibility, etc. - Paul: some changes on rootfs, all of them in master. There were a couple of issues, they are merged now as well. Things are looking reasonably good there. Looking at some QT bugs now. Work in conjunction with recipe work. A bunch of cleanup work, created a simple wiki page. Next week continue on bugs. - Michael: working on problems of down network interfaces under heavy load. They are working now. Will be watching closely. Centralized logging setup now. Central logging server is working. Wiki, networking change is coming up. LF moving YP to a quieter subnet. This week renumbering internal addresses, should not notice any downtime. Bug stats, not matching in the wiki, working with LaurentiuP, Converting into charts. RP: ssates changes: if we use different OS such as ubuntu and fedora, sstate checksum could have problems due to different libs, etc., we fixed this issue. Migration of existing structures may not be that important at this point. It will just use the new structure. Laurentiu: relocatable SDK, 2383 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Debug with gdbserver
I am trying to debug a userpsace application that misbehaves under poky-tiny. My current approach is use gdbserver on the target and attach to the offending process, then connect to it on the client using the yocto-built native gdb for the target. I can easily add gdbserver to the target image, and can successfully connect it to the process: # From the target (qemux86) root shell: # dropbearkey -t rsa -f ./rsa # dropbear -r ./rsa # DBPID=$(ps | grep dropbear | head -n1 | cut -f4 -d ' ') # gdbserver 127.0.0.1:1234 --attach $DBPID Now on the host machine (amd64) I want to: $ gdb (gdb) target extended-remote 127.0.0.1:1234 Which package do I need to build to get the appropriate gdb for the host to remote debug processes on the target? -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Debug with gdbserver
On Jul 31, 2012, at 7:46 PM, Darren Hart wrote: > I am trying to debug a userpsace application that misbehaves under > poky-tiny. My current approach is use gdbserver on the target and attach > to the offending process, then connect to it on the client using the > yocto-built native gdb for the target. > > I can easily add gdbserver to the target image, and can successfully > connect it to the process: > > # From the target (qemux86) root shell: > # dropbearkey -t rsa -f ./rsa > # dropbear -r ./rsa > # DBPID=$(ps | grep dropbear | head -n1 | cut -f4 -d ' ') > # gdbserver 127.0.0.1:1234 --attach $DBPID > > Now on the host machine (amd64) I want to: > $ gdb > (gdb) target extended-remote 127.0.0.1:1234 > > Which package do I need to build to get the appropriate gdb for the host > to remote debug processes on the target? bake cross-gdb for your arch and use it same way as above > -- > Darren Hart > Intel Open Source Technology Center > Yocto Project - Technical Lead - Linux Kernel > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Debug with gdbserver
On 07/31/2012 08:13 PM, Khem Raj wrote: > > On Jul 31, 2012, at 7:46 PM, Darren Hart wrote: > >> I am trying to debug a userpsace application that misbehaves under >> poky-tiny. My current approach is use gdbserver on the target and attach >> to the offending process, then connect to it on the client using the >> yocto-built native gdb for the target. >> >> I can easily add gdbserver to the target image, and can successfully >> connect it to the process: >> >> # From the target (qemux86) root shell: >> # dropbearkey -t rsa -f ./rsa >> # dropbear -r ./rsa >> # DBPID=$(ps | grep dropbear | head -n1 | cut -f4 -d ' ') >> # gdbserver 127.0.0.1:1234 --attach $DBPID >> >> Now on the host machine (amd64) I want to: >> $ gdb >> (gdb) target extended-remote 127.0.0.1:1234 >> >> Which package do I need to build to get the appropriate gdb for the host >> to remote debug processes on the target? > > bake cross-gdb for your arch and use it same way as above ERROR: Nothing PROVIDES 'cross-gdb' gdb-cross maybe? Ah that gets a lot farther... and then do_compile fails. | libgdb.a(python.o): In function `gdbpy_target_wide_charset': | python.c:(.text+0x1c7): undefined reference to `PyUnicodeUCS4_Decode' And a lot more similar to that. I'm doing this on poky-tiny (so a minimal target libc... shouldn't impact native bits though right? Will beat on it some more in the morning. -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/4] update emgd driver recipe and yocto-kernel for crownbay BSP
On Sun, 2012-07-29 at 06:59 -0700, nitin.a.kam...@intel.com wrote:
> From: Nitin A Kamble
>
> The following changes since commit 7bd163e41f6b861448ab19a13ded4b7c48e16641:
>
> gnu-efi_3.0m.bb: Fix tabs with spaces in python snippet (2012-07-27
> 11:41:17 -0700)
>
> are available in the git repository at:
> git://git.yoctoproject.org/meta-intel-contrib nitin/work
> http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/work
>
> Nitin A Kamble (4):
> emgd-driver-bin: upgrade from 1.10 to 1.14
> crownbay: customize the xorg.conf for the flat panel on the kit
> crownbay: add recipe extension for linux-yocto-3.4
> crownbay: make v3.4 the default kernel
Build- and runtime-tested (2d, 3d graphics and video all work well).
All except the xorg.conf patch merged into meta-intel/master, thanks.
Tom
> ...-driver-bin_1.10.bb => emgd-driver-bin_1.14.bb} | 17 +
> meta-crownbay/README |8
> meta-crownbay/conf/machine/crownbay-noemgd.conf|2 +-
> meta-crownbay/conf/machine/crownbay.conf |2 +-
> .../xserver-xf86-config/crownbay/xorg.conf | 14 ++
> .../recipes-kernel/linux/linux-yocto_3.4.bbappend | 20
>
> 6 files changed, 49 insertions(+), 14 deletions(-)
> rename common/recipes-graphics/xorg-xserver/{emgd-driver-bin_1.10.bb =>
> emgd-driver-bin_1.14.bb} (88%)
> create mode 100644
> meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Debug with gdbserver
On Jul 31, 2012, at 8:47 PM, Darren Hart wrote: > > > On 07/31/2012 08:13 PM, Khem Raj wrote: >> >> On Jul 31, 2012, at 7:46 PM, Darren Hart wrote: >> >>> I am trying to debug a userpsace application that misbehaves under >>> poky-tiny. My current approach is use gdbserver on the target and attach >>> to the offending process, then connect to it on the client using the >>> yocto-built native gdb for the target. >>> >>> I can easily add gdbserver to the target image, and can successfully >>> connect it to the process: >>> >>> # From the target (qemux86) root shell: >>> # dropbearkey -t rsa -f ./rsa >>> # dropbear -r ./rsa >>> # DBPID=$(ps | grep dropbear | head -n1 | cut -f4 -d ' ') >>> # gdbserver 127.0.0.1:1234 --attach $DBPID >>> >>> Now on the host machine (amd64) I want to: >>> $ gdb >>> (gdb) target extended-remote 127.0.0.1:1234 >>> >>> Which package do I need to build to get the appropriate gdb for the host >>> to remote debug processes on the target? >> >> bake cross-gdb for your arch and use it same way as above > > ERROR: Nothing PROVIDES 'cross-gdb' > > gdb-cross maybe? > I meant cross gdb not the exact recipe name :) > Ah that gets a lot farther... and then do_compile fails. > > | libgdb.a(python.o): In function `gdbpy_target_wide_charset': > | python.c:(.text+0x1c7): undefined reference to `PyUnicodeUCS4_Decode' > > And a lot more similar to that. I'm doing this on poky-tiny (so a > minimal target libc... shouldn't impact native bits though right? shouldn't it seems you need python native > > > Will beat on it some more in the morning. > > -- > Darren Hart > Intel Open Source Technology Center > Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Debug with gdbserver
On Tue, Jul 31, 2012 at 08:47:47PM -0700, Darren Hart wrote: > > > On 07/31/2012 08:13 PM, Khem Raj wrote: > > > > On Jul 31, 2012, at 7:46 PM, Darren Hart wrote: > > > >> I am trying to debug a userpsace application that misbehaves under > >> poky-tiny. My current approach is use gdbserver on the target and attach > >> to the offending process, then connect to it on the client using the > >> yocto-built native gdb for the target. > >> > >> I can easily add gdbserver to the target image, and can successfully > >> connect it to the process: > >> > >> # From the target (qemux86) root shell: > >> # dropbearkey -t rsa -f ./rsa > >> # dropbear -r ./rsa > >> # DBPID=$(ps | grep dropbear | head -n1 | cut -f4 -d ' ') > >> # gdbserver 127.0.0.1:1234 --attach $DBPID > >> > >> Now on the host machine (amd64) I want to: > >> $ gdb > >> (gdb) target extended-remote 127.0.0.1:1234 > >> > >> Which package do I need to build to get the appropriate gdb for the host > >> to remote debug processes on the target? > > > > bake cross-gdb for your arch and use it same way as above > > ERROR: Nothing PROVIDES 'cross-gdb' > > gdb-cross maybe? > > Ah that gets a lot farther... and then do_compile fails. > > | libgdb.a(python.o): In function `gdbpy_target_wide_charset': > | python.c:(.text+0x1c7): undefined reference to `PyUnicodeUCS4_Decode' > > And a lot more similar to that. I'm doing this on poky-tiny (so a > minimal target libc... shouldn't impact native bits though right? http://patchwork.openembedded.org/patch/33345/ Cheers, -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-ti] [HOB] issue
Hi, When i use the HOB functionality in yocto with the meta-ti, I get an error message after about 5% with no error message in it. I can only press close. I use the default layers but I do see that HOB re-arranges them into: Poky/meta Poky/meta-hob Poky/meta-ti Poky/meta-yocto I see that I can build using the command line so it has to be something with HOB and not necessary something in yocto. Thanks in advance, Kind regards, Tim -Original Message- From: Denys Dmytriyenko [mailto:de...@ti.com] Sent: dinsdag 31 juli 2012 22:11 To: Tim Verstraete Cc: meta...@yoctoproject.org Subject: Re: [meta-ti] [HOB] issue On Tue, Jul 31, 2012 at 12:04:37PM +, Tim Verstraete wrote: > Hi, > > When i use the HOB functionality in yocto with the meta-ti, I get an > error message after about 5% with no error message in it. I can only press > close. > > I use the default layers but I do see that HOB re-arranges them into: > Poky/meta > Poky/meta-hob > Poky/meta-ti > Poky/meta-yocto > > I see that I can build using the command line so it has to be > something with HOB and not necessary something in yocto. Well, HOB _is_ part of Yocto anyway. While meta-ti may be triggering the issue in HOB, you better off reporting it to the main yocto mailing list - feel free to copy meta-ti as well. -- Denys ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [for denzil] kernel.bbclass: Copy bounds.h only if it exists, needed for 2.6.x.
Shouldn't this be sent to the oe-core list?!?!?
Op 31 jul. 2012, om 22:35 heeft sidebranch.openembed...@gmail.com het volgende
geschreven:
> From: Leon Woestenberg
>
> Linux 2.6.x kernels did not (all) have the bounds.h file, so copy
> only iff exists.
>
> (See OE-Core 02ac0d1b65389e1779d5f95047f761d7a82ef7a4)
>
> Signed-off-by: Leon Woestenberg
> ---
> meta/classes/kernel.bbclass |5 +
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index c21ab96..5f6ff66 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -183,6 +183,11 @@ kernel_do_install() {
> cp arch/powerpc/lib/crtsavres.o
> $kerneldir/arch/powerpc/lib/crtsavres.o
> fi
>
> + # Necessary for building modules like compat-wireless.
> + if [ -f include/generated/bounds.h ]; then
> + cp include/generated/bounds.h
> $kerneldir/include/generated/bounds.h
> + fi
> +
> # Remove the following binaries which cause strip errors
> # during do_package for cross-compiled platforms
> bin_files="arch/powerpc/boot/addnote arch/powerpc/boot/hack-coff \
> --
> 1.7.0.4
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
