Booting Pandaboard from SD card

Samuel Stirtzel s.stirtzel at googlemail.com
Mon Oct 17 10:44:21 EDT 2011


2011/10/13 Sascha Hauer <s.hauer at pengutronix.de>:
> On Thu, Oct 13, 2011 at 10:49:30AM +0200, Samuel Stirtzel wrote:
>> 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 at 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?
>
> I just compiled the current master branch with panda_defconfig and this
> does not happen on my board. Instead I get a null pointer exception in
> the mmc driver. I just sent out a patch which fixes this.
Like Fabian hinted, i used the version with the 2011.10.0 tag and
applied the unaligned access patch.

>
> Have you changed your config?

Only the boot arguments have been changed, I used the tool bareboxenv,
something like:
./scripts/bareboxenv ./arch/arm/boards/panda/env/ ~/barebox-test/myenv-panda
and copied it as bareboxenv to the SD card.

This step was shown in a tutorial (can't find the link right now),
should I use the defaultenv instead?
If I would use the defaultenv, can I do it like:
scripts/bareboxenv ./defaultenv/ ~/barebox-test/myenv-panda
Or is there another way to do it?

>
>>
>>
>> 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.
>
> Does not work for me aswell, although with a current v3.1-rc9 kernel.
> Here's what I get with earlyprintk:
>
> Uncompressing Linux... done, booting the kernel.
> [    0.463745] GPMC revision 6.0
> [   59.033691] INFO: rcu_sched_state detected stall on CPU 0 (t=7680 jiffies)
>
> After this no more messages.
>
> Haven't investigated further so far, but maybe the kernel expects some GPMC
> registers to be set correctly.
I disabled GPMC in the kernel, with u-boot it worked* on my 2.6.35
Linux (plus some TI patches).

* Not totally since I got framebuffer problems, but that is another
problem and not the fault of the bootloader.

>
> Sascha
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>



-- 
Regards
Samuel



More information about the barebox mailing list