[U-Boot] UBI on NAND flash again

Stefan Roese
2009-06-04T08:15:30Z

On Thursday 04 June 2009 10:06:55 Daniel Mack wrote:
> > I have to admit that I never used it this way. Using "ubi part" on an
> > erased partition works fine. I suggest you give it a try.
>
> Hmm. That still doesn't work for me, and I still wonder about the
> 'attaching mtd1 to ubi0' string, which looks like a mismatch to me.

I would have to check in more details here. But I'm pretty sure this is not
the reason for your failure. Here a log from one of mine UBI systems:

=> mtdparts

device nand0 <nand>, # parts = 6
#: name size offset mask_flags
0: u-boot 0x00080000 0x00000000 0
1: env 0x00040000 0x00080000 0
2: kernel 0x00200000 0x000c0000 0
3: rootfs 0x01000000 0x002c0000 0
4: fs 0x02000000 0x012c0000 0
5: ubifs 0x04d40000 0x032c0000 0

active partition: nand0,0 - (u-boot) 0x00080000 @ 0x00000000

defaults:
mtdids : nand0=nand
mtdparts: mtdparts=nand:512k(u-
boot),256k(env),2m(kernel),16m(rootfs),32m(fs),-(ubifs)
=> nand erase 2c0000 1000000

NAND erase: device 0 offset 0x2c0000, size 0x1000000
Skipping bad block at 0x004e0000
Erasing at 0x12a0000 -- 100% complete.
OK
=> ubi part rootfs
Creating 1 MTD partitions on "nand0":
0x002c0000-0x012c0000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: empty MTD device detected
UBI: create volume table (copy #1)
UBI: create volume table (copy #2)
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 16 MiB
UBI: number of good PEBs: 127
UBI: number of bad PEBs: 1
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 121
UBI: total number of reserved PEBs: 6
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 0/0
=>

> Any idea?

Sorry, no. You need to further debug this problem to see where the failure is
generated.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================