From: Whitney, Scott <scwhitn@amazon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for Texas Instruments AM65X - add 2nd toolchain?
Date: Thu, 10 Oct 2019 13:56:45 +0000 [thread overview]
Message-ID: <1570715805181.62328@amazon.com> (raw)
We are trying to set up Buildroot to create our cross-compilation toolchain, Linux image, and root filesystem for the Texas Instruments AM65X family.
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.
The rest of our project and the remainder of U-Boot can be built using the AArch64 ARM compiler, which we have selected as our Buildroot toolchain, along with glibc.
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?
We are also trying to create everything using a br2-external tree so that all of Buildroot does not need to be checked in. We would only have to check out our br2-external tree, copy a specific version of Buildroot into it the same top-level directory as the location of our br2-external tree, and then use "make BR2_EXTERNAL=<path to our br2-external tree> our_defconfig", followed by the usual "make" to build everything.
Examples of how to go about this (e.g. Config.in.host, *.mk files, etc.) if it's feasible would be greatly appreciated.
Many thanks,
Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191010/e46561bb/attachment.html>
next reply other threads:[~2019-10-10 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 13:56 Whitney, Scott [this message]
2019-10-10 14:32 ` [Buildroot] Buildroot for Texas Instruments AM65X - add 2nd toolchain? Ryan Barnett
2019-10-10 19:28 ` Thomas Petazzoni
2019-10-10 19:41 ` Ryan Barnett
2019-10-10 14:33 ` Thomas Petazzoni
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=1570715805181.62328@amazon.com \
--to=scwhitn@amazon.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.