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