From: Patrick Agrain <patrick.agrain@alcatel-lucent.fr>
To: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 errors - are these normal?
Date: Wed, 19 Dec 2007 10:13:04 +0100 [thread overview]
Message-ID: <4768E0A0.5080700@alcatel-lucent.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0712190858010.21948@lnxricardw.se.axis.com>
Hi Ramesh ,
What Flash from ST have you tested ? Is it a 256MBytes ? Large Pages
(2048 bytes) ?
What is the marking on the chip ?
Thanks in advance.
Regards,
Patrick Agrain
Ricard Wanderlof a écrit :
> On Tue, 18 Dec 2007, Ramesh wrote:
>
>> Hi,
>>
>> I am using linux 2.6.19 and ST micro NAND chip (256M) on a PowerPC
>> platform. After booting the OS, we install firmware on to the flash.
>> These firmware images are RPM packages. Once some packages are
>> installed, we start getting some ECC errors. I guess that's fine but
>> after a few more RPM installs, the errors seem more serious. Here's a
>> sample:
>
> You shouldn't be getting ECC errors that quickly, on a chip like that I
> would expect it would take many months before you'd see an ECC error if
> ever.
>
> My guess without knowing more would be that there is a hardware problem
> causing the communication with the nand chip to fail ever so often.
>
>> The jffs2 image is created with the following flags: -e 0x20000 -s
>> 0x1000 -b -v -p -n
>> Then I use sumtool with -e 0x20000 -b -p.
>
> If the device mounts properly then there shouldn't be much wrong with the
> image.
>
> /Ricard
> --
> Ricard Wolf Wanderlöf ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden www.axis.com
> Phone +46 46 272 2016 Fax +46 46 13 61 30
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2007-12-19 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 15:43 JFFS2 errors - are these normal? Ramesh
2007-12-19 8:00 ` Ricard Wanderlof
2007-12-19 9:13 ` Patrick Agrain [this message]
2007-12-19 15:23 ` Ramesh
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=4768E0A0.5080700@alcatel-lucent.fr \
--to=patrick.agrain@alcatel-lucent.fr \
--cc=linux-mtd@lists.infradead.org \
/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