From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for Texas Instruments AM65X - add 2nd toolchain?
Date: Thu, 10 Oct 2019 16:33:30 +0200 [thread overview]
Message-ID: <20191010163330.358f056d@windsurf> (raw)
In-Reply-To: <1570715805181.62328@amazon.com>
Hello Scott,
On Thu, 10 Oct 2019 13:56:45 +0000
"Whitney, Scott" <scwhitn@amazon.com> wrote:
> We'd also like to create U-Boot, but for the AM65X, U-Boot has at
> least one piece (tiboot3.bin) that runs on a 32-bit ARM R5 core,
> requiring a 32-bit ARM cross-compiler. That piece configures some
> hardware like the DRAM controller and then loads some 64-bit code
> U-Boot code into DRAM, after which an A53 64-bit core starts running
> it.
This piece of software is bare metal, so there's no need for a Linux
capable toolchain. We have the same problem on other platforms.
A patch series was submitted in February tosolve this problem:
http://lists.busybox.net/pipermail/buildroot/2019-February/242251.html
People keep asking for this. I guess I should take my evening tonight
to finally rework this patch series, and send a new iteration of it.
> Has anyone used Buildroot with the AM65X? Is it feasible to
> build/configure a 2nd toolchain (32-bit ARM) within Buildroot,
> possibly as an additional host package?
See the above patch series, which does exactly that.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-10 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 13:56 [Buildroot] Buildroot for Texas Instruments AM65X - add 2nd toolchain? Whitney, Scott
2019-10-10 14:32 ` Ryan Barnett
2019-10-10 19:28 ` Thomas Petazzoni
2019-10-10 19:41 ` Ryan Barnett
2019-10-10 14:33 ` Thomas Petazzoni [this message]
2019-10-10 15:56 ` Whitney, Scott
2019-10-10 16:54 ` Christian Stewart
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=20191010163330.358f056d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.