From: Samuel Stirtzel <s.stirtzel@googlemail.com>
To: barebox@lists.infradead.org
Subject: Booting Pandaboard from SD card
Date: Thu, 13 Oct 2011 10:49:30 +0200 [thread overview]
Message-ID: <CAGiJk9ePXFCwosqXUtU9yzGPmmZ5O6R_9gFtJXnJ9=DUnCpOxg@mail.gmail.com> (raw)
Hi,
currently I try to get a Pandaboard to boot out of Barebox, so far I
got Barebox up and running.
For testing purpose I'd like to boot from a SD card, optimal would be
if I could set up the card like the description in the Omappedia
tutorial [1].
Is there a tutorial how to set up barebox to boot from SD cards?
What I already tried:
In the configuration file from arch/arm/boards/panda/env is the
description for a network boot configuration,
I used this file to start out and wanted to boot from the barebox prompt.
Barebox is build from my toolchain and i copy the MLO file, the
barebox.bin and the bareboxenv file to the boot partition of the card.
For convenience I currently use a precompiled MLO that has been made
for u-boot thus I just renamed the barebox.bin file to u-boot.bin.
On startup the following messages were displayed:
-
Texas Instruments X-Loader 1.5.1 (Sep 6 2011 - 13:37:48)
Reading boot sector
Loading u-boot.bin from mmc
barebox 2011.10.0 (Oct 13 2011 - 09:45:17)
Board: Texas Instrument's Panda
PandaBoard Revision: 003
ehci@ehci0: USB EHCI 1.00
Malloc space: 0x8d000000 -> 0x8f000000 (size 32 MB)
Stack space : 0x8cff8000 -> 0x8d000000 (size 32 kB)
running /env/bin/init...
not found
-
For me it looks like i forgot to copy a file or something, any advice?
Although booting the uImage with bootm looks ok it won't work, the
following message was displayed:
-
Verifying Checksum ... OK
Image Name: Angstrom/2.6.35.7/omap4430-panda
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3688408 Bytes = 3.5 MB
Load Address: 80008000
Entry Point: 80008000
OK
Starting kernel ...
commandline: <NULL>
arch_number: 2791
Uncompressing Linux... done, booting the kernel.
-
The screen just stays blank after the last message.
This looks to me like it is (obviously) caused by an incorrect
environment loaded.
Help would be appreciated.
[1] http://www.omappedia.com/wiki/Minimal-FS_SD_flashing (using 2
partitions, one for boot files and the other for the rootfs)
--
Regards
Samuel
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2011-10-13 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 8:49 Samuel Stirtzel [this message]
2011-10-13 9:07 ` Samuel Stirtzel
2011-10-13 9:14 ` Fabian van der Werf
2011-10-13 9:29 ` Samuel Stirtzel
2011-10-13 9:45 ` Samuel Stirtzel
2011-10-14 7:17 ` Fabian van der Werf
2011-10-13 9:36 ` Uwe Kleine-König
2011-10-13 15:25 ` Sascha Hauer
2011-10-17 14:44 ` Samuel Stirtzel
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='CAGiJk9ePXFCwosqXUtU9yzGPmmZ5O6R_9gFtJXnJ9=DUnCpOxg@mail.gmail.com' \
--to=s.stirtzel@googlemail.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