[U-Boot] issue with 'ubi part'

Andre Schwarz andre.schwarz at matrix-vision.de
Fri Mar 4 11:46:36 CET 2011


Stefan,

> Andre,
>
> On Friday 04 March 2011 11:16:50 Andre Schwarz wrote:
>>>> =>   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 have no real idea then why this fails in U-Boot, sorry. What versions of U-
> Boot and Linux are you using?
I'm running TOT with kernel 2.6.34.7
> I suggest you debug a bit, to see where this error results from.
ok - so no obvious mistakes.

Will try a bisect because it has been working back in November 2010.

>
>> 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 ?
> IIRC, it's because the NOR flash partitions are enumerated first. So 2 NOR
> partitions (0...1) makes the first NAND partition #2.

ok - will have a look.


-- 

Regards,
Andre



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


More information about the U-Boot mailing list