From: Kamel BOUHARA <k.bouhara@gmail.com>
To: barebox@lists.infradead.org
Subject: Re: NAND Boot Issue
Date: Tue, 18 Oct 2011 11:44:24 +0200 [thread overview]
Message-ID: <CAM9uW_6jkYxF3eVb9cK4RLnq8owJ==b3sR+JosxQ1Hf4S2r0pQ@mail.gmail.com> (raw)
In-Reply-To: <20111018082356.GJ18141@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2102 bytes --]
>
> Unaligned partitions are fine, but the partition code should mark
> them as readonly.
>
>
That's why I was unable to erase it getting -EINVAL, things are clear now
It works fine, my kernel is booting :) !
Thank you Sascha
2011/10/18 Sascha Hauer <s.hauer@pengutronix.de>
> 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 |
>
--
__________________________________
*Kamel BOUHARA*
7 rue Jules César
02100 SAINT-QUENTIN
06.17.83.29.04
[-- Attachment #1.2: Type: text/html, Size: 3329 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-10-18 9:44 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
2011-10-18 9:44 ` Kamel BOUHARA [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='CAM9uW_6jkYxF3eVb9cK4RLnq8owJ==b3sR+JosxQ1Hf4S2r0pQ@mail.gmail.com' \
--to=k.bouhara@gmail.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