Hi Luca, On 19.12.2012 16:56, Luca Ceresoli wrote: > Hi Andreas, > > Andreas Bießmann wrote: > ... >>> Creating 1 MTD partitions on "nand0": >>> 0x000000100000-0x000010000000 : "mtd=3" >>> 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 error: ubi_wl_init_scan: no enough physical eraseblocks (0, need 1) >>> >>> Now the device is totally blocked, and power cycling does not change >>> the result. >> >> have you tried to increase the malloc arena in u-boot >> (CONIG_SYS_MALLOC_LEN)? >> We had errors like this before [1],[2] and [3], maybe others - >> apparently with another error message, but please give it a try. We know >> ubi recovery needs some ram and 1MiB may be not enough. > > Thanks for your suggestion. > > Unfortunately this does not seem to be the cause of my problem: I tried > increasing my CONFIG_SYS_MALLOC_LEN in include/configs/dig297.h from > (1024 << 10) to both (1024 << 12) and (1024 << 14), but without any > difference.
Well, ok ... Malloc arena is always my first thought if I read about problems with ubi in u-boot. Have you looked up the differences in drivers/mtd/ubi/ in your u-boot and linux tree? Maybe you can see something obviously different in the ubi_wl_init_scan()? Best regards Andreas Bießmann _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
