Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] STM32F767ZI Nucleo
Date: Thu, 20 Sep 2018 10:03:28 +0200	[thread overview]
Message-ID: <20180920100328.3d5ff046@windsurf> (raw)
In-Reply-To: <f844ef8357b0480a9d8e8cf8e1414c44@baur.at>

Hello,

On Thu, 20 Sep 2018 07:35:09 +0000, Czybor Michael wrote:

> i'am new with Buildroot. I have some experiences with Petalinux from Xilinx. Now I will "create" a linux image for my STM32-Board.
> 
> I have a Windows 7 PC and a VMWare-Ubuntu-Machine.
> 
> 1.)    Is there a Buildroot-Config for my Board?

No, and from a quick read the STM32F767ZI Nucleo doesn't seem to have
external RAM, so only the RAM inside the MCU is available, and its size
is insufficient to run Linux. Are you sure it is possible to run Linux
on this specific board ?

We have existing configurations for two other STM32 boards, which have
external RAM, and are therefore able to run Linux:

  configs/stm32f429_disco_defconfig
  configs/stm32f469_disco_defconfig

> 2.)    I made an example image with a STM32F4-Config, in the Output directory where several files. What is the meaning of that files?

Please read the Buildroot manual and the slides at
https://bootlin.com/doc/training/buildroot/buildroot-slides.pdf.
There's plenty of documentation available that explains what's in the
output/ folder.

> 3.)    What is the right tool to "Flash" the output files to my board?

It depends on your board.

> 4.)    How can I debug and develop an app on the running linux image made with Buildroot and can I use VisualGDB for that purpose?

If you can indeed run Linux (see point 1), then you can do
remote debugging, as explained in
https://bootlin.com/doc/training/buildroot/buildroot-slides.pdf slide
275 and following.

I had never heard of VisualGDB, but I guess it's just an UI on top of
GDB, so you should be able to do remote debugging as well.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-09-20  8:03 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 [this message]
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

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=20180920100328.3d5ff046@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox