Skip to contentSkip to conversation

getting started...

DISCUSSION Ed Sutter 3 participants 4 messages May 27, 2015 – Jun 1, 2015

lore
Share & tools
lore

Ed Sutter

author
#0 lore raw

Hi,
I'm new to Yocto. I've used it to build/install linux on the Wandboard, and I've installed host-based cross devlopement environment (bitbake -c populate_sdk ). Everything worked, but basically I just followed some "getting started" steps so, I still don't really have a clue...

Last year I finished up a custom iMX6-based project using buildroot for rootfs, ftp.denx.de for uboot and freescale git for the kernel.

These two projects are totally isolated; yet I'm sure >85% of the code base is identical.

This year I have two ongoing iMX6 based linux projects, and may need to use a beaglebone or RPi for some other small project.

The point of the above detail is that I'd like to backup a bit and attempt to use Yocto to organize all four of these with one instance of Yocto/Poky. Is that practical? Seems to me that is the ideal goal of Yocto, but I don't see many BSPs listed under the project downloads page. On the other hand, I know wandboard and sabresd and many others do have yocto build environments.

What's the scoop on that?

I'd really like to manage all of these projects under one umbrella if possible; but what if different projects use different versions of poky (for example)?

Thanks in advance for any info...
Ed

#1 lore raw

Hi Ed,

Quoted 8 lines · Ed Sutter

This year I have two ongoing iMX6 based linux projects, and may need to use a beaglebone
or RPi for some other small project.

The point of the above detail is that I'd like to backup a bit and attempt to use Yocto to
organize all four of these with one instance of Yocto/Poky. Is that practical?

Yes, that would be a great idea!Have a look at angstrom, for example:
http://www.angstrom-distribution.org. They build one distro for a whole bunch of different machines. As such, they start with a whole bunch of different layers, most of which are BSP layers, and then simply do:

$ MACHINE=<machine> bitbake <image>

e.g.

$ MACHINE=raspberrypi2 bitbake angstrom-image
$ MACHINE=beaglebone bitbake angstrom-image
...

and build the exact same image for a bunch of different boards/machines.

They've recently switched to using a repo manifest (which I think is a great idea): https://github.com/Angstrom-distribution/angstrom-manifest

I've been playing around with doing essentially the same thing for a "poky" distribution here (but it's still a work-in-progress and not really ready for prime time yet): https://github.com/twoerner/layer-repos

Quoted 4 lines

Seems
to me that is the ideal goal of Yocto, but I don't see many BSPs listed under the project
downloads page.

Take a look here:
http://layers.openembedded.org/layerindex/branch/master/layers this is the "master" list of all the "known" layers, recipes, etc. As you can see, there are quite a few BSP layers.

Best regards,
Trevor

#2 lore raw
Quoted 36 lines · On Friday 29 May 2015 14:41:37 Trevor Woerner wrote:

Hi Ed,

Quoted 8 lines · Ed Sutter

This year I have two ongoing iMX6 based linux projects, and may need to use a beaglebone
or RPi for some other small project.

The point of the above detail is that I'd like to backup a bit and attempt to use Yocto to
organize all four of these with one instance of Yocto/Poky. Is that practical?

Yes, that would be a great idea!Have a look at angstrom, for example:
http://www.angstrom-distribution.org. They build one distro for a whole bunch of different machines. As such, they start with a whole bunch of different layers, most of which are BSP layers, and then simply do:

$ MACHINE=<machine> bitbake <image>

e.g.

$ MACHINE=raspberrypi2 bitbake angstrom-image
$ MACHINE=beaglebone bitbake angstrom-image
...

and build the exact same image for a bunch of different boards/machines.

They've recently switched to using a repo manifest (which I think is a great idea): https://github.com/Angstrom-distribution/angstrom-manifest

I've been playing around with doing essentially the same thing for a "poky" distribution here (but it's still a work-in-progress and not really ready for prime time yet): https://github.com/twoerner/layer-repos

Quoted 2 lines

Seems

Quoted 8 lines
Quoted 3 lines

to me that is the ideal goal of Yocto, but I don't see many BSPs listed under the project
downloads page.

Take a look here:
http://layers.openembedded.org/layerindex/branch/master/layers this is the "master" list of all the "known" layers, recipes, etc. As you can see, there are quite a few BSP layers.

Furthermore, you can click on the "Machines" tab i.e.

http://layers.openembedded.org/layerindex/branch/master/machines/

Type in a keyword (or leave the box empty to see all) and hit Search, and you'll see a list of the matching machines provided by all the layers in the index.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
author
#3 lore raw
Quoted 45 lines · Paul Eggleton
Quoted 35 lines · On Friday 29 May 2015 14:41:37 Trevor Woerner wrote:

Hi Ed,

Quoted 8 lines · Ed Sutter

This year I have two ongoing iMX6 based linux projects, and may need to use a beaglebone
or RPi for some other small project.

The point of the above detail is that I'd like to backup a bit and attempt to use Yocto to
organize all four of these with one instance of Yocto/Poky. Is that practical?

Yes, that would be a great idea!Have a look at angstrom, for example:
http://www.angstrom-distribution.org. They build one distro for a whole bunch of different machines. As such, they start with a whole bunch of different layers, most of which are BSP layers, and then simply do:

$ MACHINE=<machine> bitbake <image>

e.g.

$ MACHINE=raspberrypi2 bitbake angstrom-image
$ MACHINE=beaglebone bitbake angstrom-image
...

and build the exact same image for a bunch of different boards/machines.

They've recently switched to using a repo manifest (which I think is a great idea): https://github.com/Angstrom-distribution/angstrom-manifest

I've been playing around with doing essentially the same thing for a "poky" distribution here (but it's still a work-in-progress and not really ready for prime time yet): https://github.com/twoerner/layer-repos

Quoted 2 lines

Seems

Quoted 7 lines
Quoted 3 lines

to me that is the ideal goal of Yocto, but I don't see many BSPs listed under the project
downloads page.

Take a look here:
http://layers.openembedded.org/layerindex/branch/master/layers this is the "master" list of all the "known" layers, recipes, etc. As you can see, there are quite a few BSP layers.

Furthermore, you can click on the "Machines" tab i.e.

Quoted 9 lines

http://layers.openembedded.org/layerindex/branch/master/machines/

Type in a keyword (or leave the box empty to see all) and hit Search, and you'll see a list of the matching machines provided by all the layers in the index.

Cheers,
Paul

Trevor & Paul,
Ok, thanks much. I'll dig into this more now.
By the way, the page that gave me the impression there were very few BSPs is this: https://www.yoctoproject.org/downloads/bsps
Clicking on "Board Support Packages" and using <Any> and <ARM> for "YP Core Release" and "Processor Family" respectively.

Signature · 4 lines
Ed Sutter
Alcatel-Lucent Technologies -- Bell Laboratories
Phone: 908-582-2351
Email: [email protected]