Thanks Khem, At the moment I simply want to build a headless minimal install for a Beaglebone Black. Once I achieve this I plan to customize the distro for my device. Here is what I am finding confusing:
This link <https://www.yoctoproject.org/downloads/bsps/pyro23/beaglebone> looks to be the place to start. It is the "download" page for the Beaglebone. It lists, as a build system, Poky 2.3. It lists as a download "git://git.yoctoproject.org/meta-yocto -b pyro" which in turn contains, as subdirectories, meta-poky, meta-yocto, and meta-yocto-bsp. But these three directories already exist when I check out poky. If I ignore this for the moment the layer index suggests that a dependency is openembedded-core. Has this been merged in to Poky or must I clone this as well? meta-ti isn't mentioned. If I search for meta-ti I find this BSP <https://www.yoctoproject.org/product/meta-ti-bsp-layer> which makes me think that perhaps this work has been merged in to meta-yocto-bsp as no recent version of Poky is supported. Regarding the tags: If I check out the pyro branch of poky am I getting something that is stable and has been tested? I thought perhaps the tags with `pyro-17.0.0` would point to stable tested commit. The reason I'm trying to sort all of this out is that when I ran a `bitbake core-image-minimal` with Poky Pyro it failed. It was missing u-image. All I did was clone Poky/Pyro and set the MACHINE to beaglebone. It got pretty far though. It seems to have built the kernel and the device tree binaries. No signs of the root filesystem or the bootloader (u-image): core-image-base-beaglebone-20170621162619.testdata.json core-image-base-beaglebone.testdata.json core-image-minimal-beaglebone-20170624014756.testdata.json core-image-minimal-beaglebone.testdata.json modules--4.10.9+git0+ad2e885015_fe0fb8da3d-r0-beaglebone-20170621162619.tgz modules-beaglebone.tgz zImage zImage--4.10.9+git0+ad2e885015_fe0fb8da3d-r0-am335x-bone-20170621162619.dtb zImage--4.10.9+git0+ad2e885015_fe0fb8da3d-r0-am335x-boneblack-20170621162619.dtb zImage--4.10.9+git0+ad2e885015_fe0fb8da3d-r0-beaglebone-20170621162619.bin zImage-am335x-boneblack.dtb zImage-am335x-bone.dtb zImage-beaglebone.bin On Mon, Jun 26, 2017 at 5:18 PM Khem Raj <raj.k...@gmail.com> wrote: > On Mon, Jun 26, 2017 at 4:35 PM, Kenny Koller > <ke...@understoryweather.com> wrote: > > I'm trying to figure out which set of meta layers I need to build a > distro > > and images for a Beaglebone Black. > > > > I cloned poky and within I see meta-yocto and meta-yocto-bsp. The latter > has > > recipes for the Beaglebone. > > > > I also found this page which suggests cloning meta-yocto: > > > > https://www.yoctoproject.org/downloads/bsps/pyro23/beaglebone > > > > Then there is meta-ti. Where does this fit in? > > yocto project used beaglebone black as one of its reference boards > so you can find a default reference yocto BSP for it. > > Secondly, meta-ti is TI BSP layer which also supports beaglebone black > since the board is from TI > > > > > > Also when I clone say poky should I checkout the branch or a specific > tag? > > > > you can use git clone git://git.yoctoproject.org/poky -b pyro > for getting latest stable release. > > > It's not clear to me the best way start with a piece of hardware then > > determine the correct layers. > > I would suggest to do a bit more investigation as to what you need. > meanwhile you can build yocto reference BSP and play with it. There > are many packages that meta-ti would have that you might need depending > upon what you plan to do. > > > > > Thanks. > > > > > > -- > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto