public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001839] Fix for wrong setup of flash memory parts for different Olimex LPC-2294 boards Date: Mon, 06 May 2013 20:08:00 -0000 [thread overview] Message-ID: <bug-1001839-777-Jr66w8GsYl@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001839-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001839 Sergei Gavrikov <sergei.gavrikov@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergei.gavrikov@gmail.com --- Comment #1 from Sergei Gavrikov <sergei.gavrikov@gmail.com> --- (In reply to comment #0) > Created attachment 2228 [details] > Patch for Olimex LPC-2294 boards that fixes flash configuration > > In the current flash driver for Olimex LPC-2294 boards, the wrong flash > memory type was selected for certain boards (i.e. for Olimex LPC-E2294-1MB). Uwe, this driver does describe *the first H/W revision* of Olimex LPC-E2294 board. That development board (green silk. PCB) had TE28F320C3BD70 FLASH and CL8900A LAN controller (I got a mail with that PCB in 2005 :-) > The Olimex boards can have two flash configurations: > > TE28F160C3BD70 C3 INTEL FLASH > > or > > TE28F320C3BD70 C3 INTEL FLASH > > Only two boards (LPC-L2294-8MB and LPC-H2294) have the 4MB Intel 28F320C3 > parts. This was wrong in the old implementation (I stumbeld across this > issue wehn building Redboot for LPC-E2294-1MB). The attached patch fixes > this issue and adds a table in the documentation, that shows the > configurations more clearly. Your workaround makes that old olpce2294 target be "new" one (Olimex LPC-E2294-1MB Rev. B). Unfortunately, H/W Revision "B" has and different LAN controller (DM9000E) not only FLASH parts. So, FLASH I/O and networking won't be work on old LPC-E2294 board (olpce2294 BSP in eCos AnonCVS). By other hand, Olimex does not sell that old H/W anymore, perhaps, we have to add some CYGHWR* definition in-side olpce2294 hal for Revision "B" boards, e.g. CYGHWR_BOARD_OLPCE2294RB and check this definition in the flash/eth drivers. By a chance, in 2009 I had re-worked HAL for some Olimex LPC-X2294 boards and made olpcx22xx package: https://bitbucket.org/tickling/olpcx22xx Unfortunately, that package is not consistent with existing CVS code (thought it can replace it) at least, there is a basic support and for Olimex LPC-E2294 Rev. B board there. -- You are receiving this mail because: You are the assignee for the bug.
prev parent reply other threads:[~2013-05-06 20:08 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-06 5:14 [Bug 1001839] New: " bugzilla-daemon 2013-05-06 20:08 ` bugzilla-daemon [this message]
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=bug-1001839-777-Jr66w8GsYl@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.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: linkBe 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).