Home/Support/Support Forum/ConnectCore 6UL SBC Pro 1GB Installation error (ubi0 error: ubi_read_volume_table: the layout volume was not found)
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

ConnectCore 6UL SBC Pro 1GB Installation error (ubi0 error: ubi_read_volume_table: the layout volume was not found)

0 votes
I made an image in the Yocto 3.0 environment.

I tried to install the image on the 6UL Pro 1G board, but there is an error.

Attached is the environmental information below and the error message.

Please give me a lot of advice.


=> mtdparts

device nand0 <gpmi-nand>, # parts = 7
#: name size offset mask_flags
0: bootloader 0x00500000 0x00000000 0
1: environment 0x00300000 0x00500000 0
2: safe 0x00100000 0x00800000 0
3: linux 0x01800000 0x00900000 0
4: recovery 0x02000000 0x02100000 0
5: rootfs 0x20000000 0x04100000 0
6: update 0x1bf00000 0x24100000 0

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

defaults:
mtdids : nand0=gpmi-nand
mtdparts:
=>


=> printenv
arch=arm
baudrate=115200
board=ccimx6ulsbc
board_id=136
board_name=ccimx6ulsbc
board_version=3
boot_fdt=yes
bootargs_mmc_linux=setenv bootargs console=${console},${baudrate} ${bootargs_linux} root=${mmcroot} ${mtdparts}${bootargs_once} ${extra_bootargs}
bootargs_nand_linux=setenv bootargs console=${console},${baudrate} ${bootargs_linux} ${mtdparts} ubi.mtd=${mtdlinuxindex} ubi.mtd=${mtdrootfsindex} root=ubi1_0 rootfstype=ubifs rw ${bootargs_once} ${extra_bootargs}
bootargs_nfs=if test ${ip_dyn} = yes; then bootargs_ip="ip=dhcp";else bootargs_ip="ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off";fi;
bootargs_nfs_linux=run bootargs_nfs;setenv bootargs console=${console},${baudrate} ${bootargs_linux} root=/dev/nfs ${bootargs_ip} nfsroot=${serverip}:${rootpath},v3,tcp ${mtdparts} ${bootargs_once} ${extra_bootargs}
bootargs_tftp=if test ${ip_dyn} = yes; then bootargs_ip="ip=dhcp";else bootargs_ip="ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off";fi;
bootargs_tftp_linux=run bootargs_tftp;setenv bootargs console=${console},${baudrate} ${bootargs_linux} root=/dev/nfs ${bootargs_ip} nfsroot=${serverip}:${rootpath},v3,tcp ${mtdparts} ${bootargs_once} ${extra_bootargs}
bootcmd=if run loadscript; then source ${loadaddr};fi;
bootdelay=1
btaddr=00:04:f3:ff:ff:fc
console=ttymxc4
cpu=armv7
dboot_kernel_var=zimage
eth1addr=00:04:f3:ff:ff:fd
ethaddr=00:04:f3:ff:ff:fa
ethprime=FEC0
fdt_addr=0x83000000
fdt_file=imx6ul-ccimx6ulsbc.dtb
fdt_high=0xffffffff
fileaddr=80800000
filesize=8cf4000
hwid_0=4021e5e4
hwid_1=48900440
initrd_addr=0x83800000
initrd_file=uramdisk.img
initrd_high=0xffffffff
install_linux_fw_sd=if load mmc 0 ${loadaddr} install_linux_fw_sd.scr;then source ${loadaddr};fi;
install_linux_fw_usb=usb start;if load usb 0 ${loadaddr} install_linux_fw_usb.scr;then source ${loadaddr};fi;
ipaddr=192.168.42.30
linux_file=dey-image-qt-x11-ccimx6ulsbc.boot.ubifs
loadaddr=0x80800000
loadscript=if test -z "${mtdbootpart}"; then setenv mtdbootpart linux;fi;if ubi part ${mtdbootpart}; then if ubifsmount ubi0:${mtdbootpart}; then ubifsload ${loadaddr} ${script};fi;fi;
mmcroot=/dev/mmcblk1p2 rootwait rw
module_variant=0x04
mtdbootpart=linux
mtddevname=bootloader
mtddevnum=0
mtdids=nand0=gpmi-nand
mtdlinuxindex=3
mtdparts=mtdparts=gpmi-nand:5m(bootloader),3m(environment),1m(safe),24m(linux),32m(recovery),512m(rootfs),-(update)
mtdrecoveryindex=4
mtdrootfsindex=5
mtdupdateindex=6
netmask=255.255.0.0
partition=nand0,0
recovery_file=recovery.img
recoverycmd=setenv mtdbootpart recovery;boot
rootfs_file=dey-image-qt-x11-ccimx6ulsbc.ubifs
rootpath=/exports/nfsroot-ccimx6ulsbc
script=boot.scr
serverip=192.168.42.1
soc=mx6
uboot_file=u-boot.imx
update_addr=0x80800000
vendor=digi
verifyaddr=a0400000
wlanaddr=00:04:f3:ff:ff:fb
zimage=zImage-ccimx6ulsbc.bin

Environment size: 2815/131067 bytes
=>

=> run install_linux_fw_sd
..
715776 bytes read in 62 ms (11 MiB/s)
Writing bootstream...OK
Saving Environment to NAND... Erasing NAND...
Erasing at 0x500000 -- 100% complete.
Writing to NAND... OK
OK
resetting ...

..
Saving Environment to NAND... Erasing redundant NAND...
Erasing at 0x520000 -- 100% complete.
Writing to redundant NAND... OK
OK
..
NAND erase.part: device 0 offset 0x900000, size 0x1800000
Erasing at 0x20e0000 -- 100% complete.
OK
8634368 bytes read in 400 ms (20.6 MiB/s)

NAND erase.part: device 0 offset 0x900000, size 0x1800000
Erasing at 0x20e0000 -- 100% complete.
OK
ubi0: attaching mtd4
ubi0: scanning is finished
ubi0: empty MTD device detected
ubi0: attached mtd4 (name "linux", size 24 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: 192, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 0/0, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 180, total reserved PEBs: 12, PEBs reserved for bad PEB handling: 8
No size specified -> Using max size (22855680)
Creating dynamic volume linux of size 22855680
8634368 bytes written to volume linux
Verifying firmware...
Update was successful

>> Installing recovery

NAND erase.part: device 0 offset 0x2100000, size 0x2000000
Erasing at 0x40e0000 -- 100% complete.
OK
12697600 bytes read in 572 ms (21.2 MiB/s)

NAND erase.part: device 0 offset 0x2100000, size 0x2000000
Erasing at 0x40e0000 -- 100% complete.
OK
ubi0: detaching mtd4
ubi0: mtd4 is detached
ubi0: attaching mtd5
ubi0: scanning is finished
ubi0: empty MTD device detected
ubi0: attached mtd5 (name "recovery", size 32 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: 256, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 0/0, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 241, total reserved PEBs: 15, PEBs reserved for bad PEB handling: 11
No size specified -> Using max size (30601216)
Creating dynamic volume recovery of size 30601216
12697600 bytes written to volume recovery
Verifying firmware...
Update was successful


>> Installing Linux root file system



NAND erase.part: device 0 offset 0x4100000, size 0x20000000
Erasing at 0x240e0000 -- 100% complete.
OK
147800064 bytes read in 6312 ms (22.3 MiB/s)

NAND erase.part: device 0 offset 0x4100000, size 0x20000000
Erasing at 0x240e0000 -- 100% complete.
OK
ubi0: detaching mtd5
ubi0: mtd5 is detached
ubi0: attaching mtd6
ubi0: scanning is finished
ubi0 error: ubi_read_volume_table: the layout volume was not found
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd6, error -22
UBI error: cannot attach mtd6
UBI error: cannot initialize UBI, error -22
UBI init error 22
Please check, if the correct MTD partition is used (size big enough?)
syntax error
Error writing firmware!
[ERROR] Failed to update rootfs partition!

Aborted.
=>
asked Mar 29 in ConnectWare Manager by youngs New to the Community (1 point)

Please log in or register to answer this question.

...