From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Barbier, Renaud" <renaud.barbier@abaco.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: barebox 2019.07 ubiformat
Date: Fri, 27 Sep 2019 08:44:05 +0200 [thread overview]
Message-ID: <20190927064405.lfcibvom2xo3awy6@pengutronix.de> (raw)
In-Reply-To: <MN2PR16MB3117311DB17F1F18B283BCE391860@MN2PR16MB3117.namprd16.prod.outlook.com>
On Thu, Sep 26, 2019 at 02:15:57PM +0000, Barbier, Renaud wrote:
> My apology, I used a model (DX1014) that we have not upstream to your repository.
> It is based on the Freescale P1014 unlike the DA923RC (MPC8544). More answer below
> Including both the DA923RC and DX1014.
>
>
>
> > >
> > > Using the version from2016.07, the NOR boot partition can be formatted (FIT
> > image) and NAND (file system) and the system boots.
> > > When using the barebox 2019-07, both storage can be formatted but when
> > booting (Linux 4.16 or 5.2) I get:
> >
> > There is no driver for this NAND controller upstream, I assume you have
> > it in your tree, right?
> [Barbier, Renaud]
> Correct. The NAND driver has not been upstream for the DA923RC.
> I have now used the DA923RC to do the same test.
>
> With barebox from 2016.07, ubiformat gives me:
> OWBOOT> / addpart -n /dev/ram0 77070336@0x10000(image)
> OWBOOT> / ls /dev/nand0
> /dev/nand0
> OWBOOT> / ubiformat -q -y /dev/nand0 -f /dev/image
> OWBOOT> /
>
> With 2019.07, ubiformat gives:
> OWBOOT> / ubiformat -y -q /dev/nand0 -f /dev/image
> ubi1: detaching mtd0 from ubi1
> ubi1: removing nand0.ubi
> ubi1: mtd0 is detached
> nand0: error -74 (ECC error) while reading 64 bytes from PEB 14:0
> nand0: error -74 (ECC error) while reading 64 bytes from PEB 15:0
> nand0: error -74 (ECC error) while reading 64 bytes from PEB 21:0
> nand0: error -74 (ECC error) while reading 64 bytes from PEB 21:512
Not all blocks seem to be unreadable. Have you looked into subpage
reads? subpage reads have been enabled in 18ea738 ("mtd: nand: Enable
subpage reads"), but on the other hand that commit is already included
in 2016.07. Anyway, maybe the old barebox doesn't do subpage reads for
some reason.
What ECC are you using, software or hardware? Is it still the same in
the new barebox or are you maybe ending up with some other ECC scheme?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-09-27 6:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 17:44 Barbier, Renaud
2019-09-26 6:41 ` Sascha Hauer
2019-09-26 14:15 ` Barbier, Renaud
2019-09-27 6:44 ` Sascha Hauer [this message]
2019-09-27 8:43 ` Barbier, Renaud
2019-10-18 14:36 ` Barbier, Renaud
2019-10-18 15:09 ` Barbier, Renaud
2019-10-21 7:52 ` Sascha Hauer
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=20190927064405.lfcibvom2xo3awy6@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=renaud.barbier@abaco.com \
/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