From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andre Schwarz <andre.schwarz@matrix-vision.de>
Date: Wed, 02 Mar 2011 16:35:09 +0100
Subject: [U-Boot] issue with 'ubi part'
Message-ID: <4D6E63AD.1040101@matrix-vision.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Stefan,

actually I have an issue with the "ubi part" command.

Situation:

MPC8377 based board with 64MiB Nor- (u-boot etc.) and 1GiB Nand-Flash 
(ubi volume).

MTD devices look like this :

=> mtdparts

device nor0 <NOR>, # parts = 2
  #: name                size            offset          mask_flags
  0: u-boot              0x00100000      0x00000000      0
  1: FPGA                0x00200000      0x00100000      0

device nand0 <NAND>, # parts = 1
  #: name                size            offset          mask_flags
  0: root                0x40000000      0x00000000      0

active partition: nor0,0 - (u-boot) 0x00100000 @ 0x00000000

defaults:
mtdids  : nor0=NOR,nand0=NAND
mtdparts: mtdparts=NOR:1M(u-boot),2M(FPGA);NAND:-(root)
=>


Setting the ubi partition to "root" fails :

=> ubi part root
Creating 1 MTD partitions on "nand0":
0x000000000000-0x000040000000 : "mtd=0"
UBI: attaching mtd2 to ubi0
UBI error: io_init: unaligned VID header shift 2
UBI error: ubi_init: cannot attach mtd2
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error -22
exit not allowed from main input shell.
=>


######################

Did another test with a single NAND device :

=> mtdparts

device nand0 <NAND>, # parts = 1
  #: name                size            offset          mask_flags
  0: root                0x40000000      0x00000000      0

active partition: nand0,0 - (root) 0x40000000 @ 0x00000000

defaults:
mtdids  : nand0=NAND
mtdparts: mtdparts=NAND:-(root)

=> ubi part root
Creating 1 MTD partitions on "nand0":
0x000000000000-0x000040000000 : "mtd=0"
Bad block table not found for chip 0
Bad block table not found for chip 0
No space left to write bad block table
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_scan_get_free_peb: no eraseblocks found
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -28
UBI init error -28
exit not allowed from main input shell.
=>


To me the mtd numbering looks wrong in both cases - specififally: 
"ubi_init: can't attach mtdX"

Any hints ? Have I missed something ?

-- 

Regards,
Andre



MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner