Am 30.09.2014 13:19, schrieb Andy Pont:
Hello Heiko,
Hmm.. I thought to see something like this:
"too large reserved_pebs %d, good PEBs %d"
I am not familiar with this HW ... I think, you have to debug into it
Changing the dbg_err() to ubi_err() and also adding a bit more output then I get:
UBI error: vtbl_check: reserved_pebs 81, ubi->good_peb_count 80 UBI error: vtbl_check: too large reserved_pebs, good PEBs 80
Use of UBI is new to me so where are the PEBs configured?
Good question ... looking into vtbl_check(), the "reserved_pebs" value is read from the record in the volume table:
reserved_pebs = be32_to_cpu(vtbl[i].reserved_pebs);
"@reserved_pebs: how many physical eraseblocks are reserved for this volume"
The "ubi->good_peb_count 80" seems correct to me.
maybe ubi image creation was bad? I can only speculate ... sorry.
bye, Heiko