mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Jerzy Grzegorek <jurekgabpl@wp.pl>
Cc: barebox@lists.infradead.org
Subject: Re: Barebox under qemu for beagleboard
Date: Thu, 27 Dec 2012 16:17:08 +0100	[thread overview]
Message-ID: <20121227151708.GA7216@game.jcrosoft.org> (raw)
In-Reply-To: <50d1a8869abc04.36394132@wp.pl>

On 12:44 Wed 19 Dec     , Jerzy Grzegorek wrote:
>    Hi,
> 
>    I was trying to run barebox-2012.12.1 under linaro-qemu 2012.12, for
>    beagleboard.
> 
>    I build MLO (omap3530_beagle_xload_defconfig) and barebox-flash-image
>    (omap3530_beagle_defconfig).
> 
>    I prepared two partitions sd image - beagle.sd.img (first partition FAT :
>    MLO, barebox.bin, barebox-flash-image, zImage;  second partition EXT3 :
>    rootfs).
> 
>    I run linaro-qemu
> 
>    qemu-system-arm -M beagle -m 256M -nographic -sd beagle.sd.img
> 
>    and I got
> 
>    barebox 2012.12.1 #1 Wed Dec 19 08:35:21 CET 2012
> 
>    Board: Texas Instrument's Beagle
>    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba ( ), page size: 2048,
>    OOB size: 64
>    omap-hsmmc omap-hsmmc0: registered as omap-hsmmc0
>    mci mci0: registered disk0
>    malloc space: 0x87bfff10 -> 0x87ffff0f (size  4 MB)
>    stack space:  0x4020f000 -> 0x4020fc00 (size  3 kB)
>    unknown boot source. Fall back to nand
>    booting from NAND
>    failed to get image size
>    booting failed
> 
>    next qemu freezes.
> 
>    Any idea?
I guess qemu does not set the boot register correctly so barebox can not
detect that you want to boot from sd and falback to nand

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2012-12-27 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 11:44 Jerzy Grzegorek
2012-12-27 15:17 ` Jean-Christophe PLAGNIOL-VILLARD [this message]

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=20121227151708.GA7216@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=jurekgabpl@wp.pl \
    /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