public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fano Ramparany <Fano.Ramparany@rd.francetelecom.fr>
To: eCos Disuss <ecos-discuss@sourceware.cygnus.com>
Cc: Gary Thomas <gthomas@cambridge.redhat.com>
Subject: Re: [ECOS] network support
Date: Wed, 14 Feb 2001 07:59:00 -0000	[thread overview]
Message-ID: <3A8AABFD.7661C7CE@rd.francetelecom.fr> (raw)
In-Reply-To: <XFMail.20010214060826.gthomas@cambridge.redhat.com>

Gary Thomas wrote:

> Using the ConfigTool
>   Select Build->Templates
>     Hardware Platform = Cirrus Logic Development Board
>     Template = RedBoot
>
>   Select Build->Packages
>     Add 'Generic FLASH memory support'
>
>   Select Build->Packages
>     Add 'Common ethernet support'
>
>   Adjust platform details for EDB7212
>
> Or, just use the attached binary image

Thank you for your help and short response time, Gary,
I've built redboot.bin using the indications for ConfigTool
(windows based) you give, loaded it into the flash. To
test it I run an hyperterminal (bauds 34800, 8-n-1).
When I ureset+wakeup the board, the terminal remains
idle, and the diag1 led doesn't light on. When I use
the redboot_EDB7212_ROM.bin binary image you've
attached to your message instead, things get better (diag1
led lights on) but I get the following error message on my
hyperterminal screen:

 +
RedBoot(tm) debug environment - built 14:11:28, Oct 26 2000
Platform: Cirrus Logic EDB7212 (ARM 720T)
Copyright (C) 2000, Red Hat, Inc.

RAM: 0x00000000-0x00fd7000
FLASH: 0xe0000000 - 0xe1000000, 128 blocks of 0x00020000 bytes ea.
FLASH configuration checksum error or invalid key
Can't get BOOTP info - network disabled!
RedBoot>

Do you know what did I wrong?

In case this might help: if instead of running an hyperterminal, I use a cygwin
bash shell from which I run arm-elf-gdb I can
load and execute he hello test example correctly.

Fano


  reply	other threads:[~2001-02-14  7:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19  8:41 Fano Ramparany
2001-01-19  9:36 ` Gary Thomas
2001-01-22  6:48   ` Fano Ramparany
2001-01-22  7:13     ` Gary Thomas
2001-01-30  2:52       ` Fano Ramparany
2001-01-30  4:34         ` Gary Thomas
2001-01-30  6:03           ` Fano Ramparany
2001-01-30  6:08             ` Gary Thomas
2001-01-30  6:25               ` Lewin A.R.W. Edwards
2001-01-30  6:31                 ` Gary Thomas
2001-01-30  6:43                   ` Lewin A.R.W. Edwards
2001-02-13  5:55               ` Fano Ramparany
2001-02-13  6:20                 ` Gary Thomas
2001-02-14  2:44                   ` Fano Ramparany
2001-02-14  5:08                     ` Gary Thomas
2001-02-14  7:59                       ` Fano Ramparany [this message]
2001-02-14  8:24                         ` Gary Thomas
2001-02-14  9:12                           ` Lewin A.R.W. Edwards
2001-02-14  9:25                             ` Gary Thomas
2001-02-14  9:32                               ` Lewin A.R.W. Edwards
2001-02-14  9:40                                 ` Gary Thomas
2001-02-14 10:28                                   ` Robin Farine
2001-02-15  6:42                           ` Fano Ramparany
2001-01-22  7:15   ` Fano Ramparany
  -- strict thread matches above, loose matches on Subject: below --
2001-01-30  6:20 James Dabbs
1999-02-10 21:23 [ECOS] Network Support Zubin Burjor Sethna
     [not found] ` < 6006B52C37ABD211AB0900805FFE9D79169230@saturn.sg.adisys.com.au >
1999-02-12 19:57   ` David J. Fiddes
1999-02-10 18:37 Wendell Thompson
1999-02-11  9:45 ` Rick Leir
     [not found]   ` < 36C2F1F1.63DE@hymarc.com >
1999-02-14  7:02     ` David J. Fiddes
1999-02-09 11:01 Gordon McFadden
     [not found] ` < Pine.LNX.4.04.9902090702270.648-100000@mailhost.westsoft-systems.com >
1999-02-10 13:22   ` David J. Fiddes
1999-02-10 21:19     ` Brendan Simon
1999-02-06 13:48 weatp
     [not found] ` < 9902069183.AA918326790@mail.syntron.com >
1999-02-08  8:26   ` Bart Veer

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=3A8AABFD.7661C7CE@rd.francetelecom.fr \
    --to=fano.ramparany@rd.francetelecom.fr \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=gthomas@cambridge.redhat.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).