From: Denys Dmytriyenko <denis@denix.org>
To: Philip Balister <philip@balister.org>
Cc: meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] Difference between beaglebone-ai64 and beaglebone-ai64-k3r5
Date: Sat, 11 Feb 2023 19:24:22 -0500 [thread overview]
Message-ID: <20230212002422.GI22689@denix.org> (raw)
In-Reply-To: <ee179ffa-ba74-be38-e519-b12d64e5a3bf@balister.org>
On Sat, Feb 11, 2023 at 01:01:00PM -0500, Philip Balister wrote:
> I'm looking at the recent update to meta-ti/kirkstone that appears to
> add support for the beaglebone ai64 and I am curious why there are two
> machines added. I'm going to see if this works ASAP!
TI K3 family of SoCs utilize a heterogeneous multicore architecture, hence the
bootflow is quite convoluted... You can read all the details from the official
docs, also referenced from below links. But, basically, before getting into
Linux on the main Aarch64 Cortex-A72 cores, it goes through init/boot and
loads and runs different pieces on 32-bit MCU Cortex-R5F core.
Which means, from OE perspective, you need to be able to build 64-bit Linux
stack as well as 32-bit bootloader and system firmware. And that means you
need 2 different toolchains. That is done with OE multiconfig and as a
byproduct, 2 machine configs. You normally don't use -k3r5 machine config
directly, as it will be automatically handled by multiconfig dependencies to
build the necessary MCU bootloader pieces...
You may want to check the first commit that introduced this split:
https://git.yoctoproject.org/meta-ti/commit/?id=f814840465358a6b5429ad20165742ac6e6e6a29
Also, the common k3r5.inc file is rather self-explanatory:
https://git.yoctoproject.org/meta-ti/tree/meta-ti-bsp/conf/machine/include/k3r5.inc
https://patchwork.yoctoproject.org/project/ti/patch/20230211234205.3042518-1-denis@denix.org/
--
Denys
next prev parent reply other threads:[~2023-02-12 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 18:01 Difference between beaglebone-ai64 and beaglebone-ai64-k3r5 Philip Balister
2023-02-12 0:24 ` Denys Dmytriyenko [this message]
2023-02-12 13:50 ` [meta-ti] " Philip Balister
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=20230212002422.GI22689@denix.org \
--to=denis@denix.org \
--cc=meta-ti@lists.yoctoproject.org \
--cc=philip@balister.org \
/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.