public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@redhat.com>
To: "Trenton D. Adams" <tadams@theone.dnsalias.com>
Cc: eCos Discussion <ecos-discuss@sourceware.cygnus.com>,
	"Trenton D. Adams" <tadams@extremeeng.com>
Subject: RE: [ECOS] ethernet download
Date: Fri, 24 Aug 2001 07:51:00 -0000	[thread overview]
Message-ID: <XFMail.20010824085915.gthomas@redhat.com> (raw)
In-Reply-To: <000701c12caa$571bd9b0$090110ac@TRENT>

On 24-Aug-2001 Trenton D. Adams wrote:
> What about it?  It only allows you to download a ROM image once, and
> then it's wiped out of FLASH, no?  If I have to download redboot every
> time, it defeats the purpose a little bit because it might not save any
> time.
> 

That's true - for the primary ROM image.  If you're looking for a faster
way to load big ROM images, rather than keeping RedBoot in place, you're
out of luck I'm sorry.

What is it that you want to have in ROM?  Will it fit alongside of RedBoot?
If so, you can keep RedBoot in there to help you download and manipulate
the FLASH (I hope it's FLASH!).  You can still execute from FLASH if you
wish, or use RedBoot commands to load & go from FLASH.

We do this sort of thing all the time with embedded Linux systems.  RedBoot
is kept for the purpose of system startup, download and FLASH management.
When the system starts, a RedBoot script is used to startup the Linux
kernel, etc.

> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of Gary Thomas
> Sent: Thursday, August 23, 2001 5:05 PM
> To: Trenton D. Adams
> Cc: eCos Discussion
> Subject: RE: [ECOS] ethernet download
> 
> 
> 
> On 23-Aug-2001 Trenton D. Adams wrote:
>> Is there a utility for my edb7111-2 for downloading ROM eCos programs
>> over ethernet?
>> 
>> It would obviously have to start with serial in order to get the
>> original ethernet driver over and then finish over ethernet.
>> 
> 
> What about RedBoot? :-)

  reply	other threads:[~2001-08-24  7:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23 14:41 Trenton D. Adams
2001-08-23 15:58 ` Gary Thomas
2001-08-24  7:38   ` Trenton D. Adams
2001-08-24  7:51     ` Gary Thomas [this message]
2001-08-24  7:59       ` Trenton D. Adams
2001-08-24  8:06         ` Gary Thomas
2001-08-24  8:22           ` Mark Salter
2001-08-24  8:24             ` Trenton D. Adams
2001-08-24  8:30               ` Gary Thomas
2001-08-24  8:32               ` Grant Edwards
2001-08-24  8:38                 ` Trenton D. Adams
2001-08-24  8:41                   ` Grant Edwards
2001-08-24  8:40                 ` Gary Thomas
2001-08-24  8:42                   ` Grant Edwards
2001-08-24  8:51                     ` Gary Thomas
2001-08-24  9:00                       ` Grant Edwards
2001-08-24  9:03                         ` Gary Thomas
2001-08-24  9:46                           ` Grant Edwards
2001-08-24  9:03                         ` Trenton D. Adams
2001-08-24  9:05                           ` Grant Edwards
2001-08-24  9:09                             ` Trenton D. Adams
2001-08-24  8:34               ` Mark Salter

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=XFMail.20010824085915.gthomas@redhat.com \
    --to=gthomas@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=tadams@extremeeng.com \
    --cc=tadams@theone.dnsalias.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).