Setting up Build-Environment for BeagleBone Black with meta-ti

Setting up Build-Environment for BeagleBone Black with meta-ti

[Sebastian]

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

Hi,

I'm struggeling to get my BBB running with meta-ti. I have a build environment setup with Ubuntu 18.04. I have started with plain yocto and everything builds fine with beaglebone-yocto.

Now I want to get in touch with the pru-icss but that is available only in meta-ti as I've read so far.

* I've cloned again poky, meta-ti and meta-arm. Into ~/yocto
* Started with source poky/oe-build-environment build
* Edited conf/local.conf

* added MACHINE ?= "am335x-evm"

* Added the layers:

* bitbake-layers add-layer ../meta-arm/meta-arm-toolchain
* bitbake-layers add-layer ../meta-arm/meta-arm
* bitbake-layers add-layer ../meta-ti

* Started the build bitbake core-image-base

What I've read so far was to use the ti2020.00 branch of meta-ti and the yocto-3.2 branch of poky.

The build completes without any error and I get the wic.zx, but when I take the content and burn it onto my SD-Card there is no dtb in the boot folder and there is also no lifesign when I'm booting the BBB with S2 pressed.

Where is my mistake?

Regards,

Sebastian

[-- Attachment #2: Type: text/html, Size: 1225 bytes --]

Re: Setting up Build-Environment for BeagleBone Black with meta-ti

[Sebastian]

[-- Attachment #1: Type: text/plain, Size: 307 bytes --]

After a second, clean run it now works for the MACHINE ?= "beaglebone".
The first run was on master for meta-ti and poky. It seems to be necessary to know witch meta-ti version is related to witch poky version because yocto-3.2 is not telling anything about the year of creation.

Regards,

Sebastian

[-- Attachment #2: Type: text/html, Size: 36497 bytes --]

Re: [meta-ti] Setting up Build-Environment for BeagleBone Black with meta-ti

[Denys Dmytriyenko]

On Thu, Apr 22, 2021 at 06:30:25AM -0700, Sebastian wrote:
> After a second, clean run it now works for the MACHINE ?= "beaglebone".
> 
> The first run was on master for meta-ti and poky. It seems to be necessary 
> to know witch meta-ti version is related to witch poky version because 
> yocto-3.2 is not telling anything about the year of creation.

OpenEmbedded and the Yocto Project use codenames to name releases. Everyone 
knows what for example Dunfell means, but very few actually remember which 
number it corresponds to, e.g. 3.1 in this case for Dunfell, which is LTS.

https://wiki.yoctoproject.org/wiki/Releases

So, when you say yocto-3.2, I actually have to look it up in the list above 
to figure out which release or branch it corresponds to, before saying that 
meta-ti has no official support for Gatesgarth.

-- 
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

Re: Setting up Build-Environment for BeagleBone Black with meta-ti

[Sebastian]

[-- Attachment #1: Type: text/plain, Size: 372 bytes --]

Thanks for the information, know I have gone backward to yocto-3.1.

To me it is not clear how to link the meta-ti tags to releases of yocto to get as you mentioned, a stable LTS base.

That was my target.

Does it mean that the meta-ti release for example ti2020.00 will fit to the corresponding yocto-3.1? As it was released in Apr 2020?

Regards,

Sebastian

[-- Attachment #2: Type: text/html, Size: 412 bytes --]

Re: Setting up Build-Environment for BeagleBone Black with meta-ti

[Sebastian]

[-- Attachment #1: Type: text/plain, Size: 160 bytes --]

My fault, haven't seen that the information I've needed was there.

Was looking only in the git tag output instead of the websites.

Regards,

Sebastian

[-- Attachment #2: Type: text/html, Size: 184 bytes --]

Re: [meta-ti] Setting up Build-Environment for BeagleBone Black with meta-ti

[Denys Dmytriyenko]

Hi, Sebastian,


On Thu, Apr 22, 2021 at 01:46:38AM -0700, Sebastian wrote:
> Hi,
> 
> I'm struggeling to get my BBB running with meta-ti. I have a build 
> environment setup with Ubuntu 18.04. I have started with plain yocto and 
> everything builds fine with beaglebone-yocto.
> 
> Now I want to get in touch with the pru-icss but that is available only in 
> meta-ti as I've read so far.
> 
> * I've cloned again poky, meta-ti and meta-arm. Into ~/yocto
> * Started with source poky/oe-build-environment build
> * Edited conf/local.conf
> 
> * added MACHINE ?= "am335x-evm"
> 
> * Added the layers:
> 
> * bitbake-layers add-layer ../meta-arm/meta-arm-toolchain
> * bitbake-layers add-layer ../meta-arm/meta-arm
> * bitbake-layers add-layer ../meta-ti
> 
> * Started the build bitbake core-image-base
> 
> What I've read so far was to use the ti2020.00 branch of meta-ti and the 
> yocto-3.2 branch of poky.

I'm not at all sure where you've read that, but it's very strange combination 
and is incorrect.

First, ti2020.00 wasn't even a production release, but it was made out of Zeus 
branch, i.e. 3.0 Yocto release.
Second, yocto-3.2 release corresponds to Gatesgarth and meta-ti has no support 
for it.

The best approach is to see where the latest release tags are being made in 
meta-ti, and/or stick to LTS releases of Yocto. In both cases that would be 
Dunfell. You might want to pin down meta-ti to 07.03.00.005 tag for now...


> The build completes without any error and I get the wic.zx, but when I take 
> the content and burn it onto my SD-Kart there is no dtb in the boot folder 
> and there is also no lifesign when I'm booting the BBB with S2 pressed.
> 
> Where is my mistake?
> 
> Regards,
> 
> Sebastian

-- 
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964