This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

EVMK2EX: EVMK2EX UBI Filesystem install : Error on booting

Part Number: EVMK2EX

Hello.

I tried to install ubi file system on EVMK2EX using uboot commands.

I changed ubi_name as "arago-base-tisdk-image-k2e-evm.ubi".

The "arago-base-tisdk-image-k2e-evm.ubi" file is from in ti-processor-sdk-linux-k2e-evm-bin-06.03.00.106.tar.xz.

And I tried on other UBI files in same directory. "arago-tiny-image-k2e-evm.ubi" and "tisdk-docker-rootfs-image-k2e-evm.ubi"

The results are same.


I ran the following commands to install UBI filesystem.

(run get_ubi_net and run burn_ubi)

====================================================================

K2E_EVM #run get_ubi_net

BOOTP broadcast 1

DHCP client bound to address 192.168.0.55
Using K2E_EMAC0 device
TFTP from server 192.168.0.61; our IP address is 192.168.0.55
Filename '//arago-base-tisdk-image-k2e-evm.ubi'.
Load address: 0x82000000
Loading: #################################################################
#################################################################
#################################################################

..........................

736.3 KiB/s
done
Bytes transferred = 130285568 (7c40000 hex)

K2E EVM # run burn_ubi

NAND erase.part: device 0 offset 0x180000, size 0x1fe80000
Skipping bad block at 0x1ff80000
Skipping bad block at 0x1ffa0000
Skipping bad block at 0x1ffc0000
Skipping bad block at 0x1ffe0000

OK

NAND write: device 0 offset 0x180000, size 0x7c40000

 130285568 bytes written: OK

=======================================================================================

K2E EVM # boot
UBI: mtd1 is detached from ubi0
Creating 1 MTD partitions on "nand0":
0x000000180000-0x000020000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: fixable bit-flip detected at PEB 549
UBI: fixable bit-flip detected at PEB 920
UBI: fixable bit-flip detected at PEB 980
UBI: volume 0 ("rootfs") re-sized from 992 to 4036 LEBs
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=2"
UBI: MTD device size: 510 MiB
UBI: number of good PEBs: 4080
UBI: number of bad PEBs: 4
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 4080
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 1/0
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:boot", error -19
UBIFS error (pid 0): ubifs_mount: Error reading superblock on volume 'ubi:boot' errno=-19!

ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
- mount 'volume-name' volume
UBIFS not mounted, use ubifs mount to mount volume first!
ubifsload - load file from an UBIFS filesystem

Usage:
ubifsload <addr> <filename> [bytes]
- load file 'filename' to address 'addr'

==========================================================================================

ubsmount could not file "ubi:boot".

How can I install file system?

UBI file which I installed is not correct one? 

Or uboot command is wrong?