From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] ARM: bcm2835: add Raspberry Pi model B board
Date: Sun, 17 Jun 2012 21:54:38 -0600 [thread overview]
Message-ID: <4FDEA67E.7080401@wwwdotorg.org> (raw)
In-Reply-To: <4FDC1CDE.1080805@gmail.com>
On 06/15/2012 11:42 PM, Graeme Russ wrote:
> Hi Stephen,
>
> On 06/07/2012 03:45 PM, Stephen Warren wrote:
>> The Raspberry Pi model B uses the BCM2835 SoC, has 256MB of RAM, contains
>> an SMSC 9512 USB LAN/Hub chip, and various IO connectors. For more details,
>> see http://www.raspberrypi.org/.
>>
>> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
>
> Now I really can't wait for my Raspberry Pi to turn up (due on 25 June)
>
> Looking forward to trying this out - any hints / traps for young players?
Mostly U-Boot on RPi works like it would anywhere else. The few things
to watch out for are:
a) Pick the correct toolchain to build with. For my branch, I assumed
everyone was building for armhf/hardfp these days, and so from the tools
repo:
https://github.com/raspberrypi/tools.git
I picked the toolchain in the x86-linux64-cross-arm-linux-hardfp
sub-directory, and adjusted the U-Boot Makefiles to suite options
required for that toolchain.
However, Oleksandr's U-Boot branch appears to rely upon the armel/softfp
toolchain in the linux-x86 sub-directory.
b) You need to appropriate stuff in config.txt on the SD card - I
apparently have:
device_tree=kernel.dtb
device_tree_address=0x100
kernel_address=0x8000
disable_commandline_tags=1
and I store U-Boot in kernel.img.
(although I think the DT-related values are irrelevant when I'm booting
U-Boot instead of a kernel)
You will of course need a 3.3v serial->something (USB or true RS232)
adapter hooked up to GPIO header pins 6/8/10 for the console, since
there's no video output support in U-Boot yet (although I suppose we
could add USB keyboard support soon...)
Oh, and you'll probably want to update the binary firmware images on
your SD card to the latest from:
https://github.com/raspberrypi/firmware.git
The following email from Oleksandr will be interesting too:
http://lists.infradead.org/pipermail/linux-rpi-kernel/2012-June/000060.html
Of course, this is all if you specifically want to use U-Boot. The
default boot process already works completely, without involving U-Boot,
but of course doesn't support e.g. network booting.
next prev parent reply other threads:[~2012-06-18 3:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 5:45 [U-Boot] [PATCH 1/2] ARM: add basic support for the Broadcom BCM2835 SoC Stephen Warren
2012-06-07 5:45 ` [U-Boot] [PATCH 2/2] ARM: bcm2835: add Raspberry Pi model B board Stephen Warren
2012-06-16 5:42 ` Graeme Russ
2012-06-18 3:54 ` Stephen Warren [this message]
2012-06-16 3:52 ` [U-Boot] [PATCH 1/2] ARM: add basic support for the Broadcom BCM2835 SoC Stephen Warren
2012-06-21 22:26 ` Stephen Warren
2012-06-22 5:05 ` Albert ARIBAUD
2012-06-22 16:23 ` Stephen Warren
2012-06-22 16:34 ` Wolfgang Denk
2012-06-22 16:36 ` Stephen Warren
2012-06-22 17:14 ` Wolfgang Denk
2012-06-22 17:29 ` Stephen Warren
2012-06-22 17:34 ` Tom Rini
2012-06-22 18:18 ` Wolfgang Denk
2012-06-22 18:30 ` Stephen Warren
2012-06-22 21:58 ` Wolfgang Denk
2012-06-22 23:18 ` Stephen Warren
2012-06-22 23:28 ` Wolfgang Denk
2012-06-22 23:31 ` Tom Rini
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=4FDEA67E.7080401@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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