From: Tim Drury <tdrury@siliconmotorsports.com>
To: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] RE: eb40a RIP
Date: Sat, 27 Jul 2002 09:03:00 -0000 [thread overview]
Message-ID: <200207271201.56861.tdrury@siliconmotorsports.com> (raw)
In-Reply-To: <000001c233f9$a42cade0$6501a8c0@s1Main2bws911>
My eb40a has risen from the ashes! Thank you James and
Min Ling for the eb40a angel images.
I wrote a small flash erase tool to erase those lower sectors
of the eb40a's flash which I couldn't do with the redboot image
I had running in the upper half of flash because the flash driver
I wrote ignored those smaller sectors. So I used the redboot
ROMRAM in the upper half of flash to upload my flash erase
tool and cleaned out the lower half of the flash chip. Then I
converted the Angel binary into an srec and loaded it with
redboot. Burned it back into the lower half of flash and my eb40a
is fully functional again.
I think I keep those Angel images and my flash erase tool around
though....
-tim
On Thursday 25 July 2002 12:37 pm, James wrote:
> I have sent to you directly the binary so as not to hog
> the mail list bandwidth. This is for
> version "EB40A V1.0" and is a binary image of the flash.
> It turned out that the angel monitor extends from
> 0x01000600 to almost 0x01013000, so it exceeds
> the first 64K of flash.
> James
> James Musselman
>
> > -----Original Message-----
> > From: Tim Drury [mailto:tdrury@siliconmotorsports.com]
> > Sent: Wednesday, July 24, 2002 7:09 AM
> > To: ecos-discuss@sources.redhat.com
> > Subject: eb40a RIP
> >
> >
> >
> > In the process of testing the flash driver with the eb40a port
> > I just created, I managed to blow away Angel in the lower half
> > of flash. I have a working copy of redboot_ROMRAM in the
> > upper half, but the flash driver programmed into it doesn't
> > see the first few sectors of the lower half of flash. This is
> > due to the issue of two different sector sizes in the AT49xxxx
> > flash chip and I simply ignored the smaller sectors.
> >
> > Does anyone with an eb40a have a binary of the Angel bootloader
> > that I can borrow? I never compiled the one that came with
> > the eb40a and the trial period for Codewarrior has expired so
> > I can't compile it now.
> >
> > If I can get that, I can write a low level driver to erase the whole
> > lower half of the flash and burn Angel back in since my current
> > redboot port cannot do that. I can use the existing redboot_
> > ROMRAM to load my little driver and fix my eb40a.
> >
> > -tim
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2002-07-27 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 7:11 [ECOS] " Tim Drury
2002-07-25 9:38 ` [ECOS] " James
2002-07-27 9:03 ` Tim Drury [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=200207271201.56861.tdrury@siliconmotorsports.com \
--to=tdrury@siliconmotorsports.com \
--cc=ecos-discuss@sources.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).