From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBI issues on SAMA5D31 NOR flash
Date: Thu, 02 Oct 2014 11:10:31 +0200 [thread overview]
Message-ID: <542D1687.7020905@denx.de> (raw)
In-Reply-To: <006301cfde19$3e253c10$ba6fb430$@pont@sdcsystems.com>
Hello Andy,
Am 02.10.2014 10:16, schrieb Andy Pont:
> Hello Heiko,
>
>>> 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"
>
> I have changed the size of the partition as defined in U-Boot and also
> reduced the maximum image size when creating the UBI image and have found a
> combination that moves me on to the next error:
>
> U-Boot> ubi part rootfs
> UBI: attaching mtd2 to ubi0
> UBI: physical eraseblock size: 131072 bytes (128 KiB)
> UBI: logical eraseblock size: 130944 bytes
> UBI: smallest flash I/O unit: 1
> UBI: VID header offset: 64 (aligned 64)
> UBI: data offset: 128
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> - Warning: 1 protected sectors will not be erased!
> UBI error: ubi_io_write: error -5 while writing 64 bytes to PEB 0:0, written
> 0 bytes
What says flinfo ? It seems you have protected sectors on
your nor flash ... you must unprotect them before using it ...
> UBI error: erase_worker: failed to erase PEB 0, error -5
> UBI error: erase_worker: bad physical eraseblock 0 detected
> UBI warning: ubi_ro_mode: switch to read-only mode
> UBI error: do_work: work failed with error code -5
> UBI error: autoresize: cannot auto-resize volume 0
> UBI error: ubi_init: cannot attach mtd2
> UBI error: ubi_init: UBI error: cannot initialize UBI, error -30
> UBI init error 30
>
> Hopefully this may be the last hurdle to overcome but somehow I think maybe
> not!
Cheer up!
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-02 9:10 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
2014-10-02 8:16 ` Andy Pont
2014-10-02 9:10 ` Heiko Schocher [this message]
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=542D1687.7020905@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.