From mboxrd@z Thu Jan  1 00:00:00 1970
From: Heiko Schocher <hs@denx.de>
Date: Wed, 01 Oct 2014 13:35:07 +0200
Subject: [U-Boot] UBI issues on SAMA5D31 NOR flash
In-Reply-To: <003101cfdca0$7ab760b0$70262210$@pont@sdcsystems.com>
References: <009101cfdc04$16a621c0$43f26540$@pont@sdcsystems.com>
	<542A33F6.9030509@denx.de>
	<005501cfdc8d$a0e18f30$e2a4ad90$@pont@sdcsystems.com>
	<542A7992.6060802@denx.de>
	<003101cfdca0$7ab760b0$70262210$@pont@sdcsystems.com>
Message-ID: <542BE6EB.4080204@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de



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
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany