Excuse me, I forgot to paste in the u-boot output: => nand info Device 0: nand0, sector size 128 KiB => nand erase NAND erase: device 0 whole chip Bad block table found at page 524224, version 0x01 Bad block table found at page 524160, version 0x01 nand_read_bbt: Bad block at 0x0000006c0000 nand_read_bbt: Bad block at 0x00000ab40000 nand_read_bbt: Bad block at 0x00000d020000 nand_read_bbt: Bad block at 0x00000d600000 nand_read_bbt: Bad block at 0x0000135a0000 nand_read_bbt: Bad block at 0x00001d500000 nand_read_bbt: Bad block at 0x00001d520000 nand_read_bbt: Bad block at 0x00001d600000 nand_read_bbt: Bad block at 0x00001d620000 nand_read_bbt: Bad block at 0x00001dea0000 nand_read_bbt: Bad block at 0x0000299e0000 nand_read_bbt: Bad block at 0x00002b8e0000 nand_read_bbt: Bad block at 0x00002cc40000 nand_read_bbt: Bad block at 0x00003b780000 nand_read_bbt: Bad block at 0x00003fb40000 nand_read_bbt: Bad block at 0x00003fbc0000 Skipping bad block at 0x006c0000 Skipping bad block at 0x0ab40000 Skipping bad block at 0x0d020000 Skipping bad block at 0x0d600000 Skipping bad block at 0x135a0000 Skipping bad block at 0x1d500000 Skipping bad block at 0x1d520000 Skipping bad block at 0x1d600000 Skipping bad block at 0x1d620000 Skipping bad block at 0x1dea0000 Skipping bad block at 0x299e0000 Skipping bad block at 0x2b8e0000 Skipping bad block at 0x2cc40000 Skipping bad block at 0x3b780000 Skipping bad block at 0x3fb40000 Skipping bad block at 0x3fbc0000 Skipping bad block at 0x3ff80000 Skipping bad block at 0x3ffa0000 Skipping bad block at 0x3ffc0000 Skipping bad block at 0x3ffe0000 OK => mtdparts device nand0 <nand>, # parts = 1 #: name size offset mask_flags 0: rootfs 0x04000000 0x00000000 0 active partition: nand0,0 - (rootfs) 0x04000000 @ 0x00000000 defaults: mtdids : nand0=nand mtdparts: mtdparts=nand:64m(rootfs) => ubi part rootfs Creating 1 MTD partitions on "nand0": 0x000000000000-0x000004000000 : "mtd=0" 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 error: ubi_io_write: error -5 while writing 512 bytes to PEB 0:512, written 0 bytes UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 1:512, written 0 bytes UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 2:512, written 0 bytes UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 3:512, written 0 bytes UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 4:512, written 0 bytes UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 5:512, written 0 bytes UBI error: ubi_init: cannot attach mtd1 UBI error: ubi_init: UBI error: cannot initialize UBI, error -5 UBI init error -5 exit not allowed from main input shell. => nand info Device 0: nand0, sector size 128 KiB => ver U-Boot 2010.03-00150-ga47a12b-dirty (Apr 23 2010 - 06:22:06) => Thanks, Edward
________________________________ From: Ewer, Edward E Sent: Friday, April 23, 2010 6:39 AM To: 'u-boot@lists.denx.de' Subject: UBI partigion in u-boot I'm using a MPC8572DS evaluation system and attempting to set up a UBI file system from u-boot. I've seen a similar thread with similar errors but my error isn't being caused by the define CONFIG_SYS_MALLOC_LEN being too small (it's set for 1M). I'm just starting with UBI/UBIFS and hoping someone could give me some insight into what may be causing these errors. Here is my u-boot output: Thanks, Edward
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
