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 11:08:46 +0200	[thread overview]
Message-ID: <20180920110846.006e31ac@windsurf> (raw)
In-Reply-To: <bd252999392341cda6bec222f0e416dc@baur.at>

Hello,

On Thu, 20 Sep 2018 09:04:01 +0000, Czybor Michael wrote:

> thank you for your quick reply.
> 
> 1.) What is the minimum RAM-Size to run linux?

It depends on how much tuning you're ready to make. Without doing a lot
of tuning, I would say 8 MB of RAM is really the minimum. And indeed
the STM32F4/STM32F7 platforms that can run Linux have 8 or 16 MB of
external RAM: https://elinux.org/STM32#STM32F4_based.

> 2.) Output files:
> 
> I read that document, before I wrote my question. I found a rootfs.cpio folder and I gues it is the rootfs.
> 
> But what is a *.bin file?

A file containing some binary stuff.

> Why I have five *.bin file versions?

I have no idea which .bin files you're talking about.

> And what is a xipImage-file?

A Linux kernel image.

> Finally, what is a *.dtb file?

A Device Tree file.

Best regards,

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

  reply	other threads:[~2018-09-20  9:08 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 [this message]
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=20180920110846.006e31ac@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