From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kamel BOUHARA <k.bouhara@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: NAND Boot Issue
Date: Tue, 18 Oct 2011 08:58:10 +0200 [thread overview]
Message-ID: <20111018065810.GH18141@pengutronix.de> (raw)
In-Reply-To: <CAM9uW_5XSrOp2LeeihMPJYzf5oyGgLWZST2msp2-EmLW-=-B8w@mail.gmail.com>
On Mon, Oct 17, 2011 at 10:31:38PM +0200, Kamel BOUHARA wrote:
> > bootu is for starting raw kernel images. Do you have such an image?
> > Normally you have an uImage (bootm) or a zImage (bootz)
>
>
> Ok so that maybe the solution because I didn't tried with the bootm .... my
> bad ! But why did I don't have the "Bad magic number" error like when I
> tried the boot command ???
A raw image does not have any magic number you could check, so the bootu
command relies on the user passing the correct image.
>
> Here is the ls /dev result:
>
> barebox:/ ls /dev/
> zero defaultenv mem
> nor0 nand0 nand_oob0
> ram0 phy0 self_raw
> self0 env_raw env0
> nor0.barebox nor0.bareboxenv nor0.kernel
> nor0.root nand0.barebox nand0.bareboxenv
> nand0.kernel nand0.root nand0.root.bb
> nand0.kernel.bb nand0.bareboxenv.bb nand0.barebox.bb
Sorry, I meant the output of 'ls -l /dev/nand0.*' to check the sizes of
your partitions.
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-10-18 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 16:03 Kamel BOUHARA
2011-10-17 19:58 ` Sascha Hauer
2011-10-17 20:31 ` Kamel BOUHARA
2011-10-18 6:58 ` Sascha Hauer [this message]
2011-10-18 7:35 ` Kamel BOUHARA
2011-10-18 8:23 ` Sascha Hauer
2011-10-18 9:44 ` Kamel BOUHARA
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=20111018065810.GH18141@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=k.bouhara@gmail.com \
/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