public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: Wilson Kwan <wilson@kinesphere.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Redboot and edb7211
Date: Thu, 19 Apr 2001 14:49:00 -0000	[thread overview]
Message-ID: <3ADF5D4A.7A777608@redhat.com> (raw)
In-Reply-To: <4.3.2.7.2.20010418222556.00b8ce10@mail.larwe.com>

"Lewin A.R.W. Edwards" wrote:
> 
> >binaries from anoncvs but when I reset the board it complains of a checksum
> >error. I see the redboot banner but after the checksum error nothing
> 
> This is PROBABLY not the problem you're experiencing, but I have had
> trouble with my EDB7212s (I have two) wherein the NOR flash [i.e. the
> bootable flash memory] will spontaneously go bad. We have one that travels
> in the field inside a working demo, and every couple of weeks it comes back
> here with corrupt flash. So my first thought when getting a checksum error
> would be just to re-flash it.

Perhaps the message is the initial checksum error reported when no Flash
Image System has been created yet. If you do a "fis init" it may just go
away.
 
> >Also I'd like to build my own redboot images. I used the windows config tool
> >to configure for ebd7xxx board and selected the redboot package. I built it
> >for ROM and flashed it to my 7211 board. When I reset it nothing happens.
> >The LED status doesn't come on...nothing. Has anyone had any experience
> >building redboot for this board?
> 
> I used the command-line tools, running under Linux, and had no problem with
> this. However note that I did find something odd with the edb7xxx
> templates: if you use the "net" template instead of using the default
> template and adding ethernet support, the result was unbootable as a ROM
> application. So I think you may have been bitten by a similar problem.
> Jonathan (I think) posted a specific list of commands for building redboot
> recently, that is the specific set of commands I used.

The best thing to do is follow the generic instructions for rebuilding
redboot in the on-line RedBoot user's guide at
http://sources.redhat.com/ecos/docs-latest/

Unfortunately there is no edb7xxx-specific section yet (Hi Gary :)), but it
should just be a case of following the generic instructions, bearing in
mind that there are configuration import files at
hal/arm/edb7xxx/current/misc which should be used.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-04-19 14:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 18:05 Wilson Kwan
2001-04-18 19:49 ` Lewin A.R.W. Edwards
2001-04-19 14:49   ` Jonathan Larmour [this message]
2001-04-19 14:53     ` Lewin A.R.W. Edwards
2001-04-19 15:12       ` Jonathan Larmour
2001-04-19 19:12         ` Wilson Kwan
2001-04-19 15:32     ` Gary Thomas
2001-04-19 15:40       ` Jonathan Larmour
2001-04-20  6:30         ` Hugo Tyson
2001-04-20  6:39           ` Gary Thomas

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=3ADF5D4A.7A777608@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=larwe@larwe.com \
    --cc=wilson@kinesphere.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).