From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Andrey Nechypurenko <andreynech@gmail.com>
Cc: "Köry Maincent" <kory.maincent@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] Building packages for Cortex M4
Date: Thu, 9 Dec 2021 15:10:54 +0100 [thread overview]
Message-ID: <20211209151054.3799fb4e@windsurf> (raw)
In-Reply-To: <CAOiXNkDn5AZBuQLnnR1tK-aW19OKmSXpv2yuDj3wxe2CTEiDiw@mail.gmail.com>
Hello Andrey,
On Wed, 8 Dec 2021 17:46:58 +0100
Andrey Nechypurenko <andreynech@gmail.com> wrote:
> I am currently playing with Avenger96 Board which is powered by
> ST32MP157 with A7 and M4 cores. Part of my system is the firmware for
> the M4 microcontroller which should be compiled with a corresponding
> variant of gcc (not the one used to compile the rest of the system)
> and placed in /lib/firmware in the rootfs/image.
>
> I am wondering if this kind of scenario (two different
> cross-compilers) is supported by Buildroot and if yes, is there any
> documentation on how to do it? If there is no "standard" way to
> achieve this, I would appreciate any recommendations.
Yes, it is possible by installing a separate bare-metal compiler using
an additional host package in Buildroot.
You can see https://github.com/bootlin/buildroot-external-st is able to
build the M4 examples from ST. Note that this BR2_EXTERNAL works with a
few patches on Buildroot itself, available at
https://github.com/bootlin/buildroot/commits/st/2021.02. One of the
change is precisely on the bare metal toolchain package.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-09 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 16:46 [Buildroot] Building packages for Cortex M4 Andrey Nechypurenko
2021-12-09 14:10 ` Thomas Petazzoni [this message]
2021-12-09 17:02 ` Andrey Nechypurenko
2021-12-10 22:10 ` Thomas Petazzoni
2021-12-13 17:49 ` Andrey Nechypurenko
2021-12-11 8:35 ` Arnout Vandecappelle
2021-12-13 17:36 ` Andrey Nechypurenko
2021-12-13 17:52 ` Yann E. MORIN
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=20211209151054.3799fb4e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=andreynech@gmail.com \
--cc=buildroot@buildroot.org \
--cc=kory.maincent@bootlin.com \
/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.