OK, I want to hear that story :) Regards, Brian

I'm trying to understand the concept of creating a recipe and having it included in the build I do. For example, suppose I want to create the meta-intel/meta-cedartrail BSP with the

this means thats what format you want for package to be spitted out. weather you want online (on device) package management is a different story

Update, I'm still not doing something right. I did a clean rebuild of core-image-base and a tar jtvf core-image-base-beagleboard.tar.bz2 reveals opkg stuff in /var/lib/opkg only. No opkg bin. I

Hi Khem, Just want to make sure I'm following you. In my local.conf I have: EXTRA_IMAGE_FEATURES_append_pn-core-image-base = "package-management" Maybe my google-fu is lacking but I searched on

I grabbed a bag of chips and a beverage ... watching this thread! I'm right behind you guys so thanks for blazing the trail. I have other TI parts to work with but starting with first BeagleBoard

So are these pre-compiled binaries that cannot be linked... or something along those lines?

s - i Or possibly: Angstrom = binutils-cross-2.20.1-r9 Yocto = binutils-cross-2.22-r2 -- ------------------------------------------------------------ Gary Thomas | Consulting

- t / 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:

k i r 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. --

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

rn re ci 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

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

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

There's a README in the meta-ti layer, follow the instructions in there.

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

add package-management to your image EXTRA_IMAGE_FEATURES_append_pn-<yourimage> = " package-management" -- -Khem

Hi, I set my conf up to build .ipk packages but then I noticed that I don't have opkg! Working with Beagleboard and running core-image-base from master branch. All of my searches turned up info

FYI: I've been testing this with both an updated 3.0 and 3.2 kernel for the 1.2 release and it seems to cause no issues. I've made the changes in the repos, and when my 1.2 pull request comes out for

Our upstream network provider is performing maintenance on a problem line card tomorrow morning. The window is between 0300 and 0600 PST (1100-1400 UTC). They will try to route around the problem, but