From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos development list <ecos-devel@ecos.sourceware.org>
Subject: Re: LPC2xxx internal flash driver
Date: Tue, 22 Feb 2011 13:03:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1102221457390.26506@sg-desktop.belvok.com> (raw)
In-Reply-To: <4D63A876.2020706@dallaway.org.uk>
I'm sorry for double post ( by mistake I rejected ecos-devel from CC )
John Dallaway wrote:
> Hi Sergei
>
> I note that Hans Rosenfeld's LPC2xxx flash driver package
> (CYGPKG_DEVS_FLASH_ARM_LPC2XXX) is not referenced by any target at
> present. There are 7 LPC2xxx targets which could potentially make use of
> this hardware package. Can you see any reason why we should not add the
> package to the various LPC2xxx target definitions in ecos.db (including
> your own contributed ports)?
>
> FYI, the driver uses a buffer ending at 0x40004000 in internal SRAM.
Hi John,
As far as I can recall the driver was not CDLized much (it was designed
only for lpc22xx parts in a mind (i.e. for its internal flash geometry:
8x8K + 2x64K + 8x8K and it manages only those last eight 8K sectors).
It seems to me it was implemented before a merge with flashv2 code. I
recall that I played with the driver in RedBoot on Olimex LPC-H2294
header board, but, I have to re-test it with nowadays CVS stuff. I will
try to do it this evening and let you know. However, I think that driver
can be used on olpch2294, olpcl2294, olpce2294 and phycore229x targets
when eCos legacy flash API is used.
Sergei
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
next prev parent reply other threads:[~2011-02-22 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 12:13 John Dallaway
2011-02-22 13:03 ` Sergei Gavrikov [this message]
2011-02-22 19:19 ` Sergei Gavrikov
2011-02-23 8:50 ` John Dallaway
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=alpine.DEB.2.00.1102221457390.26506@sg-desktop.belvok.com \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).