From: Jon Ringle <jon@ringle.org>
To: Adam Yergovich <ayergo@jkmicro.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: buffer write error (status 0x90)
Date: Mon, 9 Aug 2010 23:46:46 -0400 [thread overview]
Message-ID: <AANLkTinL1dqv9LmQ1zTCEJ46pb=jfc3=25cehHFi9wfT@mail.gmail.com> (raw)
In-Reply-To: <4C607150.6040806@jkmicro.com>
On Mon, Aug 9, 2010 at 5:21 PM, Adam Yergovich <ayergo@jkmicro.com> wrote:
> Jon Ringle wrote:
>>
>> We are replacing the discontinued Intel StrataFlash P30 flash
>> JS28F256P30T95 with the Numonyx P30-65nm flash JS28F256P30TF on our
>> boards and have a few boards with sample chips. During some testing
>> one of the boards with the Numonyx flash chip is now reporting the
>> following buffer write error (status 0x90) on every boot:
>
> I have tested swapping the lower density part and haven't had any problems
> with MTD or otherwise. I suspect you've just got a bad part or something
> else happened.
Maybe, but we have seen other incompatibilities that occurred on all
of our samples. We use Redboot as the bootloader and we found that a
Redboot image in ROM mode will hang when trying to unlock and erase a
sector. I resolved that problem by building a ROMRAM Redboot image.
next prev parent reply other threads:[~2010-08-10 3:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 21:02 buffer write error (status 0x90) Jon Ringle
2010-08-09 21:21 ` Adam Yergovich
2010-08-10 3:46 ` Jon Ringle [this message]
2010-08-24 19:48 ` Shane Volpe
2010-08-24 23:18 ` Joakim Tjernlund
2010-08-25 11:58 ` Shane Volpe
2010-08-25 12:21 ` Joakim Tjernlund
2010-08-25 14:00 ` Shane Volpe
2010-08-25 14:08 ` Joakim Tjernlund
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='AANLkTinL1dqv9LmQ1zTCEJ46pb=jfc3=25cehHFi9wfT@mail.gmail.com' \
--to=jon@ringle.org \
--cc=ayergo@jkmicro.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 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.