mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Marc Reilly" <marc@cpdesign.com.au>
To: christian.buettner@rafi.de
Cc: barebox@lists.infradead.org
Subject: RE: Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: barebox image size
Date: Tue, 17 Jul 2012 20:44:46 +1000	[thread overview]
Message-ID: <019301cd6409$31d9c110$958d4330$@cpdesign.com.au> (raw)
In-Reply-To: <OFD0402E5D.322F9E54-ONC1257A3E.00363476-C1257A3E.0036BF7D@o0802.rafi.inhouse>

Hi,

>ok i was able to preceed a little. The new error message after booting is: 
>
>Board: RAFI i.MX53 
>eth@eth0: got MAC address from EEPROM: ******** 
>NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V
8-bit) 
>Bad block table found at page 65472, version 0x01 
>Bad block table found at page 65408, version 0x01 
>nand_read_bbt: Bad block at 0x060a0000 
>Malloc space: 0x7df00000 -> 0x7fefffff (size 32 MB) 
>Stack space : 0x7def8000 -> 0x7df00000 (size 32 kB) 
>envfs: wrong magic on /dev/env0 
>running /env/bin/init... 
>not found 
>barebox:/ 

What commands are you using to erase and program the flash area?

>Environment config 
>nand_parts="512k(barebox)ro,512k(bareboxenv),4M(kernel),120M(root)" 

>board_init.c 
>devfs_add_partition("nand0", 0x00000, 0x80000, PARTITION_FIXED, "self0"); 
>devfs_add_partition("nand0", 0x80000, 0x80000, PARTITION_FIXED, "env0"); 

These partitions aren't bad block aware, from memory, I think u want
something like:

devfs_add_partition("nand0", 0x80000, 0x80000, PARTITION_FIXED, "env0_raw");
dev_add_bb_dev("env0_raw", "env0");

Cheers,
Marc


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

  reply	other threads:[~2012-07-17 10:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16  8:37 christian.buettner
2012-07-16  8:54 ` Sascha Hauer
2012-07-16  9:15   ` Antwort: " christian.buettner
2012-07-16  9:20     ` Eric Bénard
2012-07-16  9:21     ` Antwort: " Sascha Hauer
2012-07-16  9:37       ` Antwort: " christian.buettner
2012-07-16 10:30         ` Sascha Hauer
2012-07-16 12:17           ` Antwort: " christian.buettner
2012-07-16 13:47             ` Christian Kapeller
2012-07-16 13:52               ` Antwort: " christian.buettner
2012-07-16 14:25                 ` Christian Kapeller
2012-07-16 14:30                   ` Antwort: " christian.buettner
2012-07-16 14:32                   ` Eric Bénard
2012-07-16 22:29             ` Antwort: Re: Antwort: Re: Antwort: " Marc Reilly
2012-07-17  9:58               ` Antwort: " christian.buettner
2012-07-17 10:44                 ` Marc Reilly [this message]
2012-07-17 10:49                   ` Antwort: " christian.buettner

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='019301cd6409$31d9c110$958d4330$@cpdesign.com.au' \
    --to=marc@cpdesign.com.au \
    --cc=barebox@lists.infradead.org \
    --cc=christian.buettner@rafi.de \
    /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