Home/Support/Support Forum/Can't flash rootfs ubi from u-boot (CC-WMX-JN58-NE)
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Can't flash rootfs ubi from u-boot (CC-WMX-JN58-NE)

0 votes
=> env edit mtdparts
edit: mtdparts=gpmi-nand:3m(bootloader),1m(environment),1m(safe),12m(linux),14m(recovery),200m(rootfs),-(update)
=> saveenv
Saving Environment to NAND...
Erasing redundant NAND...
Erasing at 0x320000 -- 100% complete.
Writing to redundant NAND... OK
=> mtdparts

device nand0 <gpmi-nand>, # parts = 7
#: name size offset mask_flags
0: bootloader 0x00300000 0x00000000 0
1: environment 0x00100000 0x00300000 0
2: safe 0x00100000 0x00400000 0
3: linux 0x00c00000 0x00500000 0
4: recovery 0x00e00000 0x01100000 0
5: rootfs 0x0c800000 0x01f00000 0
6: update 0x01900000 0x0e700000 0

active partition: nand0,0 - (bootloader) 0x00300000 @ 0x00000000

defaults:
mtdids : nand0=gpmi-nand
mtdparts: none
=> update rootfs mmc 0 fat core-image-timebox-minimal-ccimx6ultimebox-20200922104853.rootfs.ubifs
reading core-image-timebox-minimal-ccimx6ultimebox-20200922104853.rootfs.ubifs
118468608 bytes read in 5048 ms (22.4 MiB/s)
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=5", size 200 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 1600, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 7/3, WL threshold: 4096, image sequence number: 951485552
ubi0: available PEBs: 624, total reserved PEBs: 976, PEBs reserved for bad PEB handling: 40
size > volume size! Aborting!
Error writing firmware!
=>
asked Sep 22, 2020 in Linux by rustem_valiev New to the Community (0 points)

Please log in or register to answer this question.

1 Answer

0 votes
This was answered via support case. Here is the answer:

The problem here is that, although the partition has now been successfully resized, the UBI volume inside the partition has not.

With the partition resized, execute the below command to empty the partition. A subsequent call to 'update' the partition will cause the UBIU volume to be created.

nand erase.part rootfs

Now perform the 'update', which should now be successful.
answered Sep 22, 2020 by LeonidM Veteran of the Digi Community (4,359 points)
...