From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBI issues on SAMA5D31 NOR flash
Date: Wed, 01 Oct 2014 13:35:07 +0200 [thread overview]
Message-ID: <542BE6EB.4080204@denx.de> (raw)
In-Reply-To: <003101cfdca0$7ab760b0$70262210$@pont@sdcsystems.com>
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
next prev parent reply other threads:[~2014-10-01 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 16:40 [U-Boot] UBI issues on SAMA5D31 NOR flash Andy Pont
2014-09-30 4:39 ` Heiko Schocher
2014-09-30 9:04 ` Andy Pont
2014-09-30 9:36 ` Heiko Schocher
2014-09-30 11:19 ` Andy Pont
2014-10-01 11:35 ` Heiko Schocher [this message]
2014-10-02 8:16 ` Andy Pont
2014-10-02 9:10 ` Heiko Schocher
2014-10-02 9:16 ` Andy Pont
2014-10-02 9:44 ` Andy Pont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=542BE6EB.4080204@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox