From: David Vrabel <dvrabel@arcom.com>
To: Dan Merillat <harik.attar@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: CFI Extended (Intel P30) problems on an ARM PXA255
Date: Fri, 05 May 2006 09:29:37 +0100 [thread overview]
Message-ID: <445B0CF1.8020400@arcom.com> (raw)
In-Reply-To: <c0c067900605031926w730bc9a3sed5c7eee03585b2b@mail.gmail.com>
Dan Merillat wrote:
> I originally sent this to the linux-arm list, but it's looking more
> and more like either a MTD issue, or a hardware issue with our board.
>
> We have a custom PXA255 board, based on the generic Intel reference
> design. Nothing very
> complex at all. RAM, Strataflash (P30), JTAG and a serial port is
> all I have active at this point.
>
> Everything works correctly, until I try to write to the filesystem. As
> soon as I do, I start getting JFFS corruption notices. It's fairly
> obvious what's wrong: All reads are returning 0x0080, the 'Ok' status
> bit. I can break in the jtag, write a reset to the flash, and
> continue, and new reads work properly, until I write again (or the
> original write retries).
Perhaps the cache invalidating operation in the MTD map driver you're
using is wrong?
> I thought it might be a memory timing issue, but I pulled the timing
> register (MSC0) and applied the faster timings to u-boot, and it can
> still read and write the flash properly. System speed and memory
> speed are also the same (200mhz/100mhz) for both u-boot and linux.
If you suspect memory timings may be an issue I would advise slowing the
timings under Linux to the lowest possible. The experiment you describe
here changes two variables (the software and the timings) which is not
good practice.
David Vrabel
--
David Vrabel, Design Engineer
Arcom, Clifton Road Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK Web: http://www.arcom.com/
next prev parent reply other threads:[~2006-05-05 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 2:26 CFI Extended (Intel P30) problems on an ARM PXA255 Dan Merillat
2006-05-04 2:58 ` Nicolas Pitre
[not found] ` <c0c067900605040020n74a74da8s4ed1c3cd0abc3fed@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0605040909570.28543@localhost.localdomain>
2006-05-04 18:37 ` Dan Merillat
2006-05-04 18:45 ` ext-manjunath.govindashetty
2006-05-04 19:17 ` Jared Hulbert
2006-05-05 8:29 ` David Vrabel [this message]
2006-05-05 20:48 ` Dan Merillat
2006-05-05 22:07 ` Dan Merillat
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=445B0CF1.8020400@arcom.com \
--to=dvrabel@arcom.com \
--cc=harik.attar@gmail.com \
--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