Thanks Denys. I read through the links and even your slides via the "yumminess" post on Yocto. Thanks for all the good work.
I feel like I should be building against meta-ti. This is for an actual remote product (no GUI) with several hundred instances and I'm trying to build a small distro that has just what I need. What exists is a hybrid of two debian releases and a backported kernel and I'd like to get that under control. Your post clarifies the layers but if I want to use meta-ti with Poky/Morty (presumably the correct choice) what must I do? Also this link <https://www.yoctoproject.org/product/meta-ti-bsp-layer> suggests that meta-ti is compatible with Yocto 1.6. I assume that's just outdated information.. This link <http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/about/> suggests that the layer depends on openembedded-core. Is this true or is this now folded in to Poky? I'm beginning to work on a new hardware design that integrates one of the TI Cortex-A solutions on to a single board (rather than the Beaglebone black mated to our board) so I'm motivated to sort all of this out. Best regards, Kenny On Tue, Jun 27, 2017 at 10:44 AM Denys Dmytriyenko <[email protected]> wrote: > On Tue, Jun 27, 2017 at 10:12:12AM -0700, Kenny Koller wrote: > > On Tue, Jun 27, 2017 at 9:22 AM, Denys Dmytriyenko <[email protected]> wrote: > > > > > Well, meta-ti is quite active and is current. If by current you mean > "pyro" > > > branch, then it's not an indication and there was an explanation on the > > > list. > > > > Yes. I see the activity on this list (no offense meant). New to the list > so > > probably missed any explanation. > > Activity in git: > http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/ > > Reply to "pyro" branch question: > https://lists.yoctoproject.org/pipermail/meta-ti/2017-June/010023.html > > > > > But in general, if you are not using meta-ti layer, why are you posting > > > error > > > messages to meta-ti list? > > > > Because it's not clear which layers are required for the Beaglebone build > > (as I mention in my previous response). It occurred to me that perhaps > > meta-ti must be included to build the bootloaders. As far as I can tell > > there is no explicit mention of which layers are required. I think the > > answer is that Poky includes everything that is required but my build > > failed for a reason that was unclear. > > Some time ago I gave this explanation of layers for BeagleBone: > https://lists.yoctoproject.org/pipermail/yocto/2014-October/021819.html > > Most of that still stands today and both meta-ti and meta-yocto-bsp provide > own versions of u-boot. > > > > I can hop off this list if it has nothing to do with the Beaglebone > > processor. > > meta-ti has everything to do with BeagleBone, but you are not using it. You > are using meta-yocto-bsp - it does provide upstream versions of u-boot and > the > linux kernel and normally just works for BeagleBone. What the exact issue > with > "pyro" in your case, I'm not sure. > > -- > Denys > > > > > On Tue, Jun 27, 2017 at 04:51:29AM +0000, Kenny Koller wrote: > > > > I'm not sure if I should be using it. When I look at the meta-ti > > > repository > > > > it doesn't seem current with the Poky releases. Furthermore it seems > that > > > > meta-yocto-bsp contains recipes for Beaglebone. It's not clear to me > > > which > > > > layer has a recipe for Das U-Boot. > > > > > > > > All I did was clone Poky. Checkout Pyro. Edited my local.conf to > > > > MACHINE='beaglebone'. And `bitbake core-image-minimal`. > > > > > > > > On Mon, Jun 26, 2017 at 11:53 AM Denys Dmytriyenko <[email protected]> > wrote: > > > > > > > > > Do you use meta-ti layer? > > > > > > > > > > > > > > > On Sat, Jun 24, 2017 at 02:50:32AM +0000, Kenny Koller wrote: > > > > > > Hi, > > > > > > > > > > > > I'm using 2.3 to build the minimal Beaglebone Black images. > > > > > > > > > > > > I issue the following and get the error below. Is the warning > > > regarding a > > > > > > missing bootloader config the issue? > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Kenny > > > > > > > > > > > > $ bitbake core-image-minimal > > > > > > > > > > > > | INFO: Creating image(s)... > > > > > > | > > > > > > | WARNING: bootloader config not specified, using defaults > > > > > > | > > > > > > | ERROR: _exec_cmd: install -m 0644 -D > > > > > > /home/ubuntu/yocto/poky/build/tmp/deploy/images/beaglebone/ > > > u-boot.img > > > > > > > > > > > /home/ubuntu/yocto/poky/build/tmp/work/beaglebone-poky- > > > linux-gnueabi/core-image-minimal/1.0-r0/deploy-core- > > > image-minimal-image-complete/core-image-minimal-beaglebone- > > > 20170624014756/tmp.wic.khxryxga/boot/u-boot.img > > > > > > returned '1' instead of 0 > > > > > > | output: install: cannot stat > > > > > > '/home/ubuntu/yocto/poky/build/tmp/deploy/images/ > > > beaglebone/u-boot.img': > > > > > No > > > > > > such file or directory > > > > > > | > > > > > > | WARNING: exit code 1 from a shell command. > > > > > > | ERROR: Function failed: do_image_wic (log file is located at > > > > > > > > > > > /home/ubuntu/yocto/poky/build/tmp/work/beaglebone-poky- > > > linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.12719) > > > > > > ERROR: Task > > > > > > (/home/ubuntu/yocto/poky/meta/recipes-core/images/core- > > > image-minimal.bb: > > > > > do_image_wic) > > > > > > failed with exit code '1' > > > > > > NOTE: Tasks Summary: Attempted 2263 tasks of which 2252 didn't > need > > > to be > > > > > > rerun and 1 failed. > > > > > > > > > > > > Summary: 1 task failed: > > > > > > /home/ubuntu/yocto/poky/meta/recipes-core/images/core- > > > image-minimal.bb > > > > > : > > > > > > do_image_wic > > > > > > Summary: There was 1 ERROR message shown, returning a non-zero > exit > > > code. > > > > > > > > > > > -- > > > > > > _______________________________________________ > > > > > > meta-ti mailing list > > > > > > [email protected] > > > > > > https://lists.yoctoproject.org/listinfo/meta-ti > > > > > > > > > > > > > >
-- _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
