From: Mark Salter <msalter@redhat.com>
To: lgagne@yahoo.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Problems programming Intel's J3 Stratoflash chip.
Date: Tue, 08 Jun 2004 19:20:00 -0000 [thread overview]
Message-ID: <20040608192009.422807907B@deneb.localdomain> (raw)
In-Reply-To: <20040608184330.67693.qmail@web50807.mail.yahoo.com> (message from Louis Gagne on Tue, 8 Jun 2004 11:43:30 -0700 (PDT))
>>>>> Louis Gagne writes:
> Intel has recently bumped up their revision of the
> 128Mbit J3 Stratoflash chip (28F128J3). My Redboot
> code handled the J3A version just fine, but with the
> J3C version I get errors programming it. The error is
> 0x92. This error persists even if I unlock the
> sectors before trying to program the chip.
> Has anyone else run into this issue? If so, were you
> able to overcome the problem? How did you resolve it?
This should have been fixed in CVS with this (if its the bug
I'm thinking of):
2003-10-29 Jonathan Larmour <jifl@eCosCentric.com>
* src/flash_unlock_block.c (flash_unlock_block): test lock bit
explicitly - newer flash parts use the reserved bits in the
returned data.
--Mark
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-06-08 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 18:43 Louis Gagne
2004-06-08 19:20 ` Mark Salter [this message]
2004-06-11 16:41 ` [ECOS] Can we add the intel npe package to the latest sources? (was Re: [ECOS] Problems programming Intel's J3 Stratoflash chip) Krishna Ganugapati
2004-06-11 16:57 ` [ECOS] " Mark Salter
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=20040608192009.422807907B@deneb.localdomain \
--to=msalter@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=lgagne@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).