Hi Joseph, Maybe you can use adt-installer. http://www.yoctoproject.org/docs/latest/adt-manual/adt-manual.html#using-the-adt-installer Best Regards Chong

Good day ALL, I was wondering if it's possible to automatically add QEMU dependencies (kernel and ext3 files) into the script generated by do_populate_sdk? Then after running the generated SDK script,

I have run below command bitbake -c fetchall core-image-minimal It has created downloads directory and packages source codes are there inside, but i am not able to find the kernel and u-boot source

Good day ALL, I was wondering if it's possible to automatically add QEMU dependencies (kernel and ext3 files) into the script generated by do_populate_sdk? Then after running the generated SDK script,

Also look into the buildhistory class. Philip

Hi Atul, Yes. Aarch64 support is available in meta-linaro/meta-aarch64 URL: http://git.linaro.org/?p=openembedded/meta-linaro.git You can choose between: 1. genericarmv8b - generic armv8 big endian

Hi All, Is there support for Aarch64(64 bit ARMv8) available right now? If so then what i need to mention as a MACHINE in local.conf. Please let me know with your valuable suggestion if any. Thanks

Gary,

Hello Jeff, The errors are package related. Meta-cgl can be seen as a non BSP specific layer (it can be viewed as the LSB from poky). I already started fixing a number, of the already existing

using: bitbake -g <image-name> && cat pn-depends.dot | grep -v -e '-native' | grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq you can visualize the image packages. Let me know

Hi All, I have an image deployed on gumstix board and I do not know the recipe file used to build that image. I want to know list of recipes used to build that image. Is it possible?? Thanks &

The big thing missing from this version(*) is no cape support, so if you need an LCD display or CAN driver or ..., you're not going to find it. The meta-ti version does support those AFAIK (*)

excellent. since i want to configure and build for a classroom environment and probably don't need bleeding edge, i'll stick with the yocto-bsp stuff, which has served me well thus far. rday --

The generic "it depends" answer applies here. Due to the efforts of TI,the core BBB support made it into the mainline kernel for 3.14, so that forms a common baseline of feature support. Outside of

Use the branch in refs/head instead of the tag. This allows a given tag name to differ from the branch name. Signed-off-by: Richard Leitner <richard.leitner@...> ---

Hi folks, I've ran into a problem using tag names in SRCREV for git repositories after migrating from 1.4 to 1.6.1 "daisy". Before (1.4) the following worked fine: SRCREV = "v${PV}" SRC_URI =

i want to build a bootable system for a BBB, and i can see at least three possibilities: 1) the meta-yocto-bsp layer defines the beaglebone as one of its reference boards 2) the "meta-ti"

perusing dev manual and section 5.17.1: IMAGE_FEATURES = "read-only-rootfs" or EXTRA_IMAGE_FEATURES += "read-only-rootfs" um ... isn't that backwards? should you not be appending

Hi Nicolas/Sathish, Thank you both very much for your responses. With your help, I have been able to copy the pre-compiled libraries to my image now. Cheers, Josh

Hi, While upgrading poky daisy branch to YPv1.6.1, both Brendan & I observed that there is an circular dependency issue in initscripts. Strangely, this issue is not observable if we are