From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] STM32F767ZI Nucleo
Date: Thu, 20 Sep 2018 13:11:40 +0200 [thread overview]
Message-ID: <20180920131140.3cba4968@windsurf> (raw)
In-Reply-To: <a78201d496ec473681000194f412b3da@baur.at>
Hello,
Please don't top post.
On Thu, 20 Sep 2018 09:33:48 +0000, Czybor Michael wrote:
> you wrote: " I have no idea which .bin files you're talking about."
>
> the "binary stuff" could be the bootloader, is this right?
>
> I found four versions (not five :-)):
>
> a.) stm32f429i-disco.bin
> b.) stm32f469i-disco.bin
> c.) stm32429i-eval.bin
> d.) stm32746g-eval.bin
These are built by the afboot-stm32 package, which indeed is the
bootloader for STM32 platforms. See
https://github.com/mcoquelin-stm32/afboot-stm32.
> But I started the build process only with one configuration?
afboot-stm32 builds a bootloader for all boards it supports, and we
install all of them.
> One more question about the device-tree-file. If I like to use UIO-Devices, than I must edit the device-tree.
>
> 1.) Can I use UIO-Device-Drivers?
Yes, why wouldn't you be able to use them ?
> 2.) How do I input a different device tree?
Either you patch the Device Tree in your kernel tree, or add a new one
in your kernel tree. Or you can use the option
BR2_LINUX_KERNEL_CUSTOM_DTS_PATH to point to an arbitrary Device Tree
file.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-20 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 7:35 [Buildroot] STM32F767ZI Nucleo Czybor Michael
2018-09-20 8:03 ` Thomas Petazzoni
2018-09-20 9:04 ` Czybor Michael
2018-09-20 9:08 ` Thomas Petazzoni
2018-09-20 9:33 ` Czybor Michael
2018-09-20 11:11 ` Thomas Petazzoni [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=20180920131140.3cba4968@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.