From: "Denys Dmytriyenko" <denis@denix.org>
To: Sebastian <sebastian.krahl@lacon.de>
Cc: meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] Setting up Build-Environment for BeagleBone Black with meta-ti
Date: Thu, 22 Apr 2021 15:22:49 -0400 [thread overview]
Message-ID: <20210422192249.GU15937@denix.org> (raw)
In-Reply-To: <bjdh.1619081198829695553.NA6r@lists.yoctoproject.org>
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
prev parent reply other threads:[~2021-04-22 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 8:46 Setting up Build-Environment for BeagleBone Black with meta-ti Sebastian
2021-04-22 13:30 ` Sebastian
2021-04-22 19:28 ` [meta-ti] " Denys Dmytriyenko
2021-04-23 12:49 ` Sebastian
2021-04-23 17:16 ` Sebastian
2021-04-22 19:22 ` Denys Dmytriyenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210422192249.GU15937@denix.org \
--to=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=sebastian.krahl@lacon.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.