public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: peter_lanius@yahoo.com.au
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] RedBoot image for Olimex LPC-E2294
Date: Mon, 19 Oct 2009 11:42:00 -0000	[thread overview]
Message-ID: <964415.68782.qm@web51911.mail.re2.yahoo.com> (raw)
In-Reply-To: <20091019104557.GA19013@sg-ubuntu.local>

Hi Sergei

I have the Rev B Olimex LPC-E2294 board with the LPC-2214 CPU and 1MB of Flash (MX26LV800T).

Do I need to apply all the patches from the 

bitbucket.org/tickling/olpcx22xx/

repository?

Thanks, Peter



----- Original Message ----
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: peter_lanius@yahoo.com.au
Cc: ecos-discuss@ecos.sourceware.org
Sent: Mon, 19 October, 2009 9:45:57 PM
Subject: Re: [ECOS] RedBoot image for Olimex LPC-E2294

On Mon, Oct 19, 2009 at 02:32:36AM -0700, peter_lanius@yahoo.com.au wrote:
> Hi,
> 
> I would like to use RedBoot / eCOS for my new project which is going
> to run on an Olimex LPC-E2294 board. I have built RedBoot as per the
> instructions in Anthony Massa's book (using the 'redboot' template
> for the Olimex board). The whole build went without a hitch, I used
> the Redboot_ROM.ecm configuration options file provided in the eCOS
> 3.0 distribution for the Olimex board.
> 
> I then used CrossWorks to burn the Flash image ('redboot.bin') using
> 0x00000000 as the load address. This seemed to work ok as well and
> when I restarted the board I could connect to RedBoot via
> Hyperterminal. But I do get a warning message:
>  
> FLASH: driver init failed: Invalid FLASH address
> **Warning** FLASH configuration checksum error or invalid key
> Use 'fconfig -i' to [re]initialize database
> No network interfaces found
> 
> RedBoot(tm) bootstrap and debug environment [ROM]
> Non-certified release, version v3_0 - built 19:33:12, Oct 19 2009
> ...
> Platform: Olimex LPC-E2294 development board (ARM7TDMI-S)
> RAM: 0x81000000-0x81100000 [0x8100b560-0x810f1000 available]
> RedBoot>

Hello Peter,

What's board revision do you have?
http://olimex.com/dev/lpc-e2294.html
http://olimex.com/dev/lpc-e2294rb.html

These boards have the different flash parts. eCos v3_0 has HAL for old
(Olimex now says 'obsolete board') Olimex LPC-E2294 board. If you have
the new one, i.e. Olimex LPC-E2294 REV.B board, try this HAL from here
http://bitbucket.org/tickling/olpcx22xx/

> What does the 'Invalid Flash address' message mean? Did I burn
> RedBoot into the wrong location? Should I have used the
> 'redboot.elf' file instead? Should I have modified the
> 'mlt_arm_lpc2xxx_olpce2294_rom.ldi' file (what is in there seems to
> me to also suggest the 0x00000000 start address)?

Old Olimex LPC-E2294 had 28F320C3 Intel flash parts, new boards have
28F160C3. These flash parts have the different device codes, perhaps,
eCos v3_0 flash driver for olpce2294 target cannot identify your chip.


Sergei

> Thanks
> Peter
> 
> 
> 
>       __________________________________________________________________________________
> Get more done like never before with Yahoo!7 Mail.
> Learn more: http://au.overview.mail.yahoo.com/
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



      __________________________________________________________________________________
Get more done like never before with Yahoo!7 Mail.
Learn more: http://au.overview.mail.yahoo.com/

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2009-10-19 11:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19  9:32 peter_lanius
2009-10-19 10:42 ` Sergei Gavrikov
2009-10-19 11:42   ` peter_lanius [this message]
2009-10-19 13:47     ` Sergei Gavrikov
2009-10-24  9:37       ` [ECOS] RedBoot loading eCOS examples causes PC reboot peter_lanius
2009-10-24 12:38         ` Sergei Gavrikov
     [not found]           ` <738229.12555.qm@web51906.mail.re2.yahoo.com>
2009-10-25 13:20             ` Sergei Gavrikov
2009-10-25 16:04               ` Sergei Gavrikov
2009-10-26  9:58               ` [ECOS] LPC2XXX watchdog feeds and interrupts Laurie Gellatly
2009-10-30 13:51                 ` [ECOS] Using openssl for HTTPS Laurie Gellatly
     [not found]                 ` <46171.9697145329$1256910809@news.gmane.org>
2009-10-30 14:20                   ` [ECOS] " Kelvin Lawson
2009-10-30 21:39                     ` Laurie Gellatly
     [not found]                     ` <26103.8444740281$1256938790@news.gmane.org>
2009-11-02  8:58                       ` Kelvin Lawson
2009-11-02 10:22                         ` Laurie Gellatly
2010-02-04 17:45                     ` [ECOS] pthread_kill return value Jay Foster
2010-02-08 12:36                       ` Bart Veer
2009-10-27  6:11               ` [ECOS] RedBoot loading eCOS examples causes PC reboot peter_lanius
2009-10-24 13:21         ` [ECOS] " Grant Edwards

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=964415.68782.qm@web51911.mail.re2.yahoo.com \
    --to=peter_lanius@yahoo.com.au \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=sergei.gavrikov@gmail.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).