All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: storing barebox to flash /dev/nand0
Date: Fri, 10 Sep 2010 12:30:45 +0200	[thread overview]
Message-ID: <201009101230.46079.jbe@pengutronix.de> (raw)
In-Reply-To: <AANLkTi=kFq71uyAstUiw82oV5EFt3nUv2u1JoQpO_XHR@mail.gmail.com>

Marek,

Belisko Marek wrote:
> On Fri, Sep 10, 2010 at 11:27 AM, Juergen Beisert <jbe@pengutronix.de> 
wrote:
> > Belisko Marek wrote:
> >> Hi,
> >>
> >> I'm porting barebox to mini2440 board. I can boot barebox from SDRAM
> >> by loading to TEXT_BASE address.
> >> I would like to test also booting from NAND flash but I can't find a
> >> way how to store barebox loaded in RAM
> >> to flash.
> >>
> >> I try tftp barebox.bin /dev/nand0 but if failed with:
> >>
> >> TFTP from server 10.146.1.21 ('barebox.bin' -> '/dev/nand0')
> >>         offset 0x00000200 not page aligned
> >> write: Invalid argument
> >>
> >> tftp failed: error -22
> >>
> >> How can I properly store to flash?
> >
> > Consider the bad blocks in your NAND. So, you will need a bad block aware
> > device to write to.
> >
> > This code in your board specific init routine should add the thing:
> >
> > [...]
> > /* ----------- add some vital partitions -------- */
> > devfs_add_partition("nand0", 0x00000, 0x40000, PARTITION_FIXED,
> > "self_raw"); dev_add_bb_dev("self_raw", "self0");
> >
> > devfs_add_partition("nand0", 0x40000, 0x20000, PARTITION_FIXED,
> > "env_raw"); dev_add_bb_dev("env_raw", "env0");
> > [...]
>
> OK add vital partitions but after that ls -la /dev shows:
> [...]

Not sure if this is all right (all show the barebox partition):

> crw-------     262144 self_raw

Okay, 256 kiB

> crw-------          0 self0

Hmm, 0?

> crw-------     262144 nand0.barebox

Okay, 256 kiB

> crw-------          0 nand0.barebox.bb

Again, 0?

For the environment it looks different:

> crw-------     131072 env_raw
> crw-------     131072 env0
> crw-------     131072 nand0.bareboxenv
> crw-------     131072 nand0.bareboxenv.bb

All are 128 kiB.

jbe

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

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

  reply	other threads:[~2010-09-10 10:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10  9:01 storing barebox to flash /dev/nand0 Belisko Marek
2010-09-10  9:19 ` Abdoulaye Walsimou Gaye
2010-09-10 10:01   ` Belisko Marek
2010-09-10 12:31     ` Abdoulaye Walsimou Gaye
2010-09-10 16:01     ` Robert Schwebel
2010-09-11 11:02       ` Belisko Marek
2010-09-10  9:27 ` Juergen Beisert
2010-09-10  9:53   ` Belisko Marek
2010-09-10 10:30     ` Juergen Beisert [this message]
2010-09-10 10:46       ` Belisko Marek
2010-09-10 11:01         ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-10 11:07           ` Belisko Marek
2010-09-10  9:27 ` Jean-Christophe PLAGNIOL-VILLARD

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=201009101230.46079.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=marek.belisko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.