From: Daniel Mack <daniel@caiaq.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBI on NAND flash again
Date: Wed, 3 Jun 2009 20:05:51 +0200 [thread overview]
Message-ID: <20090603180551.GL26160@buzzloop.caiaq.de> (raw)
I know there has been some traffic regaring the UBI layer recently,
however, reading the conversations didn't solve the issue I'm facing.
With a current U-Boot (git as of today) and 128MB NAND flash on a
PXA303, I get the following:
$ mtdparts
device nand0 <nand0>, # parts = 5
#: name size offset mask_flags
0: u-boot 0x00080000 0x00000000 0
1: env 0x00020000 0x00080000 0
2: splash 0x00060000 0x000a0000 0
3: kernel 0x00300000 0x00100000 0
4: ubilayer 0x07c00000 0x00400000 0
active partition: nand0,0 - (u-boot) 0x00080000 @ 0x00000000
defaults:
mtdids : nand0=nand0
mtdparts: mtdparts=nand0:512k(u-boot),128k(env),384k(splash),3M(kernel),-(ubilayer)
$ ubi part ubilayer
Creating 1 MTD partitions on "nand0":
0x00400000-0x08000000 : "mtd=4"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -12
UBI init error -12
exit not allowed from main input shell.
What puzzles me is this 'UBI: attaching mtd1 to ubi0' - shouldn't that
be 'mtd4'?
The same layout works well under Linux, btw.
Any hints?
Daniel
next reply other threads:[~2009-06-03 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 18:05 Daniel Mack [this message]
2009-06-04 6:42 ` [U-Boot] UBI on NAND flash again Stefan Roese
2009-06-04 6:50 ` Daniel Mack
2009-06-04 6:56 ` Stefan Roese
2009-06-04 8:06 ` Daniel Mack
2009-06-04 8:15 ` Stefan Roese
2009-06-04 8:51 ` Wolfgang Denk
2009-06-04 9:07 ` Daniel Mack
2009-06-04 9:17 ` Stefan Roese
2009-06-04 9:27 ` Wolfgang Denk
2009-06-04 9:37 ` Daniel Mack
2009-06-04 8:35 ` Wolfgang Denk
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=20090603180551.GL26160@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=u-boot@lists.denx.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 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.