From: "Henrik Nordström" <henrik@henriknordstrom.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building two different "SPL" for the same board?
Date: Fri, 17 May 2013 20:06:07 +0200 [thread overview]
Message-ID: <1368813967.3925.23.camel@localhost> (raw)
I am looking into reusing the SPL system initialization part for a very
minimalistic "SPL" which only initializes the board.
To give a bit of context, on the Allwinner CPUs there is a recovery boot
mode where data can be copied over USB and executed by the CPU. But most
of the board including DRAM controller is not initialized by default so
the very first thing you need to do is to upload & execute board
initialization code (but excluding CPU initialization).
Note: It is not really an SPL as all it does is initializing the board
and then returning control to the USB loader so additional code
(u-boot.bin) can be uploaded to DRAM and executed.
I have this implemented today partially out-of-tree leaching objects
from an u-boot build to build a binary with the initialization code. My
question is if it would make sense to try integrate this into the u-boot
tree somehow. Have something similar been done for any other board?
The current "code" is at
https://github.com/linux-sunxi/sunxi-tools/tree/master/felboot
mainly main.c (entry + stubs), the rest is only for a small printf and
is not needed.
Regards
Henrik
next reply other threads:[~2013-05-17 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 18:06 Henrik Nordström [this message]
2013-05-17 18:17 ` [U-Boot] Building two different "SPL" for the same board? Tom Rini
2013-05-17 20:56 ` Henrik Nordström
2013-05-22 15:26 ` Tom Rini
2013-05-23 8:53 ` Henrik Nordström
2013-05-23 9:54 ` Albert ARIBAUD
2013-05-23 20:39 ` Tom Rini
2013-05-24 1:14 ` Henrik Nordström
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=1368813967.3925.23.camel@localhost \
--to=henrik@henriknordstrom.net \
--cc=u-boot@lists.denx.de \
/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