mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Trent Piepho <tpiepho@kymetacorp.com>
To: barebox <barebox@lists.infradead.org>
Subject: Barebox on small memory systems
Date: Wed, 13 Apr 2016 00:15:36 +0000	[thread overview]
Message-ID: <1460506588.9103.26.camel@rtred1test09.kymeta.local> (raw)

I'm considering porting barebox to Altera's Arria10 SoC.  A key
difference from the existing Cyclone V support is that the SoC SDRAM
controller is part of the FPGA scanchain.  Which means that in order to
use SDRAM, the bootloader must load a file much larger than the maximum
bootloader size into the FPGA.

With Cyclone V the code needed to use SDRAM is a few kB, fits inside the
60 kB maximum bootloader size, and runs as part of the barebox PBL.  It
seems almost all other ARM SoC's also have SDRAM init code that is small
enough to fit inside barebox.  With Arria 10 the maximum bootloader size
is increased to 204 kB but the code/data needed to use SDRAM is several
MB.  So barebox will need to load it out of flash itself.

In order to get an image file out of flash and programmed into the FPGA,
it's useful to have a number of barebox drivers, like the MCI system,
partition table parsing, FAT filesystem, etc.  Basically getting the
full barebox (with a minimal set of drivers, e.g. no shell) running
without having SDRAM access.

So can one run barebox in 256 Kb?

A minimal config of a non-PBL non-relocatable barebox with the necessary
features is only about 54 Kb.  So that certainly fits.  But that doesn't
include stack, heap, bss, etc.  Can a stripped down barebox actually run
in 256 Kb and mount a FAT filesystem to get a next stage bootloader?
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2016-04-13  0:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13  0:15 Trent Piepho [this message]
2016-04-13  3:35 ` Andrey Smirnov
2016-04-26 20:34   ` Trent Piepho

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=1460506588.9103.26.camel@rtred1test09.kymeta.local \
    --to=tpiepho@kymetacorp.com \
    --cc=barebox@lists.infradead.org \
    /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