Stefan,
Hi Andre,
On Wednesday 02 March 2011 16:35:09 Andre Schwarz wrote:
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 you erase the flash partition before trying to attach UBI on it?
yes - the ubi volume has been created by linux and is working fine :
ubiformat /dev/NAND -y ubiattach /dev/ubi_ctrl -m 9 ubimkvol /dev/ubi0 -N rootfs -m mount -t ubifs ubi0:rootfs /mnt/nand
Actually I'm running Linux with rootfs on this very ubi volume.
All I wanna do is get the kernel + dtb from this volume for stand-alone boot. Meanwhile I'm getting both files using tftp from the server - but that's no long term solution.
I'm still curious why we get
0x000000000000-0x000040000000 : "mtd=0" -> 0 ! and UBI error: ubi_init: cannot attach mtd2 -> 2 !
Is this the expected behaviour ?
Regards, André
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler Registergericht: Amtsgericht Stuttgart, HRB 271090 Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner