mail archive of the barebox mailing list
 help / color / mirror / Atom feed
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 10:23:56 +0200	[thread overview]
Message-ID: <20111018082356.GJ18141@pengutronix.de> (raw)
In-Reply-To: <CAM9uW_4vV0=8ZrAy2ChFHy4oix6ouCD-aP2E=Yb3mG0KY1GGiw@mail.gmail.com>

On Tue, Oct 18, 2011 at 09:35:38AM +0200, Kamel BOUHARA wrote:
> I tried with a zImage, here is what I'm getting :
> 
> barebox:/ bootz /dev/nand0.kernel.bb
> invalid magic 0x00002018
> 
> And here the ls -l /dev/nand0.* output :
> 
>  barebox:/ ls -l /dev/nand0.*
> crw-------     393216 /dev/nand0.barebox.bb
> crw-------     131072 /dev/nand0.bareboxenv.bb
> crw-------    2883584 /dev/nand0.kernel.bb
> crw-------  533200896 /dev/nand0.root.bb
> crw-------  533667840 /dev/nand0.root
> crw-------    2764800 /dev/nand0.kernel
> crw-------     131072 /dev/nand0.bareboxenv
> crw-------     307200 /dev/nand0.barebox
> 
> Here is how I did my kernel and root partitions, following this steps :
> 
> addpart /dev/nand0 300k(barebox)ro,128k(bareboxenv),2700k(kernel),-(root)

Ok, that puts some light into this. Please make sure your partitions are
aligned to eraseblock boundaries, usually 128k. so:

addpart /dev/nand0 512k(barebox)ro,128k(bareboxenv),3M(kernel),-(root)

barebox currently does not enforce this, it's probably time to change
this. Unaligned partitions are fine, but the partition code should mark
them as readonly.
Currently we have no way of passing the eraseblocksize through to the
partition code, so it's not trivial to enforce alignment.

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

  reply	other threads:[~2011-10-18  8:23 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
2011-10-18  7:35       ` Kamel BOUHARA
2011-10-18  8:23         ` Sascha Hauer [this message]
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=20111018082356.GJ18141@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