Problem when updating T20 to Linux 2.6 UBI error

I try to update a T20 board (256 MB Ram V1.2a) to Linux V2.6 Image.

When performing command: run update I get :

reading colibri_t20/ubifs_248KiB.img

UBI: scanning is finished
UBI init error 22
resetting …

I have erased the ubi partition.
Some one an idea??

Please try the flashing from scratch procedure in the following article on our developer website.

Thanks for trying to help.
But sorry but same error…

And you did indeed do the nand erase.chip resp. nand erase.part ubi prior to run setupdate; run update as stated there? Could you please provide the full U-Boot output of all that so we can have a closer look? I just tried it on one of my modules and it works fine as expected. Do you happen to have another module you could try as well?

This time I only have that single T20 here. I have many PXA 320 but sorry only that T20

I did start the modul in recoverymode.
→ load u-boot over USB update.sh -r 256 -v V1_2 -d
→ nand erase.chip
→ cfgblock create ( entered Version / serial)
→ run setupdate
→ run update

Here a serial capture:
Colibri T20 # nand erase.chip

NAND erase.chip: device 0 whole chip

Erasing at 0x0 – 0% complete.
Skipping bad block at 0x00040000

Skipping bad block at 0x00080000

Skipping bad block at 0x000c0000

Skipping bad block at 0x00100000

Skipping bad block at 0x00140000

Skipping bad block at 0x00180000

Skipping bad block at 0x001c0000

Skipping bad block at 0x00200000

Skipping bad block at 0x00240000

Skipping bad block at 0x00280000

Skipping bad block at 0x002c0000

Skipping bad block at 0x00300000

Skipping bad block at 0x00340000

Skipping bad block at 0x00380000

Erasing at 0x500000 – 1% complete.
Erasing at 0xa00000 – 2% complete.
Erasing at 0xf40000 – 3% complete.
Erasing at 0x1440000 – 4% complete.
Erasing at 0x1980000 – 5% complete.
Erasing at 0x1e80000 – 6% complete.
Erasing at 0x23c0000 – 7% complete.
Erasing at 0x28c0000 – 8% complete.
Erasing at 0x2e00000 – 9% complete.
Erasing at 0x3300000 – 10% complete.
Erasing at 0x3840000 – 11% complete.
Erasing at 0x3d40000 – 12% complete.
Erasing at 0x4280000 – 13% complete.
Erasing at 0x4780000 – 14% complete.
Erasing at 0x4cc0000 – 15% complete.
Erasing at 0x51c0000 – 16% complete.
Erasing at 0x5700000 – 17% complete.
Erasing at 0x5c00000 – 18% complete.
Erasing at 0x6140000 – 19% complete.
Erasing at 0x6640000 – 20% complete.
Erasing at 0x6b80000 – 21% complete.
Erasing at 0x7080000 – 22% complete.
Erasing at 0x75c0000 – 23% complete.
Erasing at 0x7ac0000 – 24% complete.
Erasing at 0x7fc0000 – 25% complete.
Erasing at 0x8500000 – 26% complete.
Erasing at 0x8a00000 – 27% complete.
Erasing at 0x8f40000 – 28% complete.
Erasing at 0x9440000 – 29% complete.
Erasing at 0x9980000 – 30% complete.
Erasing at 0x9e80000 – 31% complete.
Erasing at 0xa3c0000 – 32% complete.
Erasing at 0xa8c0000 – 33% complete.
Erasing at 0xae00000 – 34% complete.
Erasing at 0xb300000 – 35% complete.
Erasing at 0xb840000 – 36% complete.
Erasing at 0xbd40000 – 37% complete.
Erasing at 0xc280000 – 38% complete.
Erasing at 0xc780000 – 39% complete.
Erasing at 0xccc0000 – 40% complete.
Erasing at 0xd1c0000 – 41% complete.
Erasing at 0xd700000 – 42% complete.
Erasing at 0xdc00000 – 43% complete.
Erasing at 0xe140000 – 44% complete.
Erasing at 0xe640000 – 45% complete.
Erasing at 0xeb80000 – 46% complete.
Erasing at 0xf080000 – 47% complete.
Erasing at 0xf5c0000 – 48% complete.
Erasing at 0xfac0000 – 49% complete.
Erasing at 0xffc0000 – 50% complete.
Erasing at 0x10500000 – 51% complete.
Erasing at 0x10a00000 – 52% complete.
Erasing at 0x10f40000 – 53% complete.
Erasing at 0x11440000 – 54% complete.
Erasing at 0x11980000 – 55% complete.
Erasing at 0x11e80000 – 56% complete.
Erasing at 0x123c0000 – 57% complete.
Erasing at 0x128c0000 – 58% complete.
Erasing at 0x12e00000 – 59% complete.
Erasing at 0x13300000 – 60% complete.
Erasing at 0x13840000 – 61% complete.
Erasing at 0x13d40000 – 62% complete.
Erasing at 0x14280000 – 63% complete.
Erasing at 0x14780000 – 64% complete.
Erasing at 0x14cc0000 – 65% complete.
Erasing at 0x151c0000 – 66% complete.
Erasing at 0x15700000 – 67% complete.
Erasing at 0x15c00000 – 68% complete.
Erasing at 0x16140000 – 69% complete.
Erasing at 0x16640000 – 70% complete.
Erasing at 0x16b80000 – 71% complete.
Erasing at 0x17080000 – 72% complete.
Erasing at 0x175c0000 – 73% complete.
Erasing at 0x17ac0000 – 74% complete.
Erasing at 0x17fc0000 – 75% complete.
Erasing at 0x18500000 – 76% complete.
Erasing at 0x18a00000 – 77% complete.
Erasing at 0x18f40000 – 78% complete.
Erasing at 0x19440000 – 79% complete.
Erasing at 0x19980000 – 80% complete.
Erasing at 0x19e80000 – 81% complete.
Erasing at 0x1a3c0000 – 82% complete.
Erasing at 0x1a8c0000 – 83% complete.
Erasing at 0x1ae00000 – 84% complete.
Erasing at 0x1b300000 – 85% complete.
Erasing at 0x1b840000 – 86% complete.
Erasing at 0x1bd40000 – 87% complete.
Erasing at 0x1c280000 – 88% complete.
Erasing at 0x1c780000 – 89% complete.
Erasing at 0x1ccc0000 – 90% complete.
Erasing at 0x1d1c0000 – 91% complete.
Erasing at 0x1d700000 – 92% complete.
Erasing at 0x1dc00000 – 93% complete.
Erasing at 0x1e140000 – 94% complete.
Erasing at 0x1e640000 – 95% complete.
Erasing at 0x1eb80000 – 96% complete.
Erasing at 0x1f080000 – 97% complete.
Erasing at 0x1f5c0000 – 98% complete.
Erasing at 0x1fac0000 – 99% complete.
Erasing at 0x1ffc0000 – 100% complete.
OK
Colibri T20 # cfgblco ock create
Is the module an IT version? [y/N]
Enter the module version (e.g. V1.1B): V1.2A
Enter module serial number: 04750977
Toradex config block successfully written
Colibri T20 # run setupdate
reading flash_blk.img
710 bytes read in 14 ms (48.8 KiB/s)

Executing script at 01000000

reading colibri_t20/flash_blk.img
2423 bytes read in 20 ms (118.2 KiB/s)

Executing script at 00408000

enter “run update” to update the entire module
Colibri T20 # run update

NAND read: device 0 offset 0x300000, size 0x64
Skipping bad block 0x00300000
Skipping bad block 0x00340000
Skipping bad block 0x00380000
100 bytes read: OK
crc32 for 00408008 … 0040800a ==> ffffff00 != 94305232 ** ERROR **

NAND read: device 0 offset 0x15c0000, size 0x40
64 bytes read: OK
crc32 for 00408008 … 0040800a ==> ffffff00 != 94305232 ** ERROR **

NAND read: device 0 offset 0x1c80000, size 0x44
64 bytes read: OK
crc32 for 00408008 … 0040800a ==> ffffff00 != 94305232 ** ERROR **

NAND read: device 0 offset 0x7380000, size 0x40
64 bytes read: OK
crc32 for 00408008 … 0040800a ==> ffffff00 != 94305232 ** ERROR **

NAND read: device 0 offset 0x7900000, size 0x40
64 bytes read: OK
crc32 for 00408008 … 0040800a ==> ffffff00 != 94305232 ** ERROR **
reading colibri_t20/colibri_t20-256-v12-nand.img
901120 bytes read in 101 ms (8.5 MiB/s)

NAND erase: device 0 offset 0x0, size 0x300000

Erasing at 0x0 – 8% complete.
Skipping bad block at 0x00040000

Skipping bad block at 0x00080000

Skipping bad block at 0x000c0000

Skipping bad block at 0x00100000

Skipping bad block at 0x00140000

Skipping bad block at 0x00180000

Skipping bad block at 0x001c0000

Skipping bad block at 0x00200000

Skipping bad block at 0x00240000

Skipping bad block at 0x00280000

Skipping bad block at 0x002c0000

OK

NAND write: device 0 offset 0x0, size 0xdc000
Skip bad block 0x00040000
Skip bad block 0x00080000
Skip bad block 0x000c0000
Skip bad block 0x00100000
Skip bad block 0x00140000
Skip bad block 0x00180000
Skip bad block 0x001c0000
Skip bad block 0x00200000
Skip bad block 0x00240000
Skip bad block 0x00280000
Skip bad block 0x002c0000
Skip bad block 0x00300000
Skip bad block 0x00340000
Skip bad block 0x00380000
901120 bytes written: OK
reading colibri_t20/ubifs_248KiB.img
166338560 bytes read in 14755 ms (10.8 MiB/s)
UBI: default fastmap pool size: 100
UBI: default fastp WL pool size: 25
UBI: attaching mtd1 to ubi0
UBI: scanning is finished
UBI init error 22
resetting …

Looks like you are trying this with one of them modules having a wrongly bad block marked NAND flash part assembled. While this is not invalid per se one would need to reserve massive amounts of blocks to actually be able to cope with this. What probably happens is that after you erased the UBI partition it gets partly overwritten by either U-Boot, its environment or the factory configuration block due to U-Boot simply skipping over all the many bad blocks at the beginning of the device. You could try scrubbing the NAND or alternatively as mentioned before adjust the flash layout.

Thanks for the Support.
Scrubbing didn’t help. I ordered a new board. Now everything works fine.

Good to hear.

Would be interesting to see exactly what goes wrong with your other module. If you would like to RMA it I will make sure you get a new one as a replacement. Just mention this thread when filling out the following form.