[U-Boot] ubi attaching error (UBI error: ubi_read_volume_table)

[naveen yadav]

Hi All,



I am using flex-onenand for my u-boot. i have added the patch for
flex-onenand and UBI and UBIFS published by kyungmin park.

I have done following steps:

1. first command
# onenand erase 0x40000 0x200000

2. second command
 # mtdparts default
3. third commad
# mtdparts
4. forth command
# ubi part u-boot
(i got error
UBI error: ubi_read_volume_table:
 the layout volume was not found
attach_by_scanning-4
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error -22 )


a) first command out put
1. # mtdparts default

---mtdparts_init---
last_ids  : onenand0=onenand
env_ids   : onenand0=onenand
last_parts: mtdparts=onenand:2m at 256k(u-boot),256k(params),2m(kernel),16m(rootfs)
,32m(fs),-(ubifs)
env_parts : mtdparts=onenand:2m at 256k(u-boot),256k(params),2m(kernel),16m(rootfs)
,32m(fs),-(ubifs)

last_partition : onenand0,0
env_partition  : <NULL>
no partition variable set, setting...
--- current_save ---
=> partition onenand0,0
--- index partitions ---

--- mtd_part_info: partition number 0 for device onenand0 (onenand)
=> mtddevnum 0,
=> mtddevname u-boot

2. second command output
# mtdparts

---mtdparts_init---
last_ids  : onenand0=onenand
env_ids   : onenand0=onenand
last_parts: mtdparts=onenand:2m at 256k(u-boot),256k(params),2m(kernel),16m(rootfs)
,32m(fs),-(ubifs)
env_parts : mtdparts=onenand:2m at 256k(u-boot),256k(params),2m(kernel),16m(rootfs)
,32m(fs),-(ubifs)

last_partition : onenand0,0
env_partition  : onenand0,0

---list_partitions---

device onenand0 <onenand>, # parts = 6
 #: name                size            offset          mask_flags
 0: u-boot              0x00200000      0x00040000      0
 1: params              0x00040000      0x00240000      0
 2: kernel              0x00200000      0x00280000      0
 3: rootfs              0x01000000      0x00480000      0
 4: fs                  0x02000000      0x01480000      0
 5: ubifs               0x3c480000      0x03480000      0

--- mtd_part_info: partition number 0 for device onenand0 (onenand)

active partition: onenand0,0 - (u-boot) 0x00200000 @ 0x00040000

defaults:
mtdids  : onenand0=onenand
mtdparts: mtdparts=onenand:2m at 256k(u-boot),256k(params),2m(kernel),16m(rootfs),3
2m(fs),-(ubifs)

3. Third command output
# ubi part u-boot

---mtdparts_init---
last_ids  : onenand0=onenand
env_ids   : onenand0=onenand
last_parts: mtdparts=onenand:2m at 256k(u-boot),256k(params),2m(kernel),16m(rootfs)
,32m(fs),-(ubifs)
env_parts : mtdparts=onenand:2m at 256k(u-boot),256k(params),2m(kernel),16m(rootfs)
,32m(fs),-(ubifs)

last_partition : onenand0,0
env_partition  : onenand0,0
448 do_ubi -1454 do_ubi -2466 do_ubi -5--- find_dev_and_part ---
id = u-boot
--- find_dev_and_part ---
id = u-boot
Creating 1 MTD partitions on "onenand0":
0x%lx-0x%lx : ""
UBI: attaching mtd1 to ubi0 ubi_attach_mtd_dev
UBI: min_io_size      2048
UBI: hdrs_min_io_size 512
UBI: ec_hdr_alsize    512
UBI: vid_hdr_alsize   512
UBI: vid_hdr_offset   512
UBI: vid_hdr_aloffset 512
UBI: vid_hdr_shift    0
UBI: leb_start        2048
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_read_volume_table:
 the layout volume was not found
attach_by_scanning-4
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error -22