From: Gary Thomas <gthomas@cambridge.redhat.com>
To: james chen <james_ch1@sina.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Memory Layout
Date: Thu, 19 Apr 2001 17:48:00 -0000 [thread overview]
Message-ID: <XFMail.20010419184820.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <000701c0c932$28f70900$c408aa0a@inc.inventec>
On 20-Apr-2001 james chen wrote:
> Hi, Thomas:
>>
>> Question: if you are building a custom board and shipping a bundled
> application
>> with it, why would you _not_ want RedBoot, even in the final product?
>>
> First, I don't know whether it will cost down the performance or not.
None.
>
> Second, it will require extra flash memory to hold it.
There would be this cost, but IMO it's minor, especially when weighed against
the flexibility and features which are available. Things like:
* Ability to debug code in the field (things _do_ break)
* Ability to update code in FLASH - RedBoot, applications, etc
* If your target has networking hardware, ability to connect via network
to the debug/bootstrap environment.
* Flexible & extensible control over the boot-time behaviour
* Support for POST and BIST
>
> Third, I want to replace redboot with my hardware check code in final
> product. when power on, it will run code to check hardware, if the hardware
> is all OK, then load eCos to RAM from flash memory and run eCos
> automatically. it seems RedBoot doesn't support it.
This mode of operation is fully supported by RedBoot and already in place on
a number of targets.
next prev parent reply other threads:[~2001-04-19 17:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 2:01 james chen
2001-04-18 5:24 ` Gary Thomas
2001-04-18 18:05 ` james chen
2001-04-19 5:12 ` Gary Thomas
2001-04-19 17:37 ` james chen
2001-04-19 17:48 ` Gary Thomas [this message]
2001-04-19 17:53 ` [ECOS] Bootloaders (was Re: [ECOS] Memory Layout) Lewin A.R.W. Edwards
-- strict thread matches above, loose matches on Subject: below --
2008-04-10 21:35 [ECOS] Memory layout Syed Ismail
2007-10-29 14:13 [ECOS] memory layout Syed Ismail
2007-10-29 14:18 ` Andrew Lunn
2003-10-08 14:29 [ECOS] Memory Layout James Yates
2003-09-18 7:31 [ECOS] Memory layout Matthieu.GIRARDIN
2002-11-18 19:44 [ECOS] memory layout AL Chane
2002-10-30 9:55 Schumacher, Gordon
2002-11-04 20:37 ` Jonathan Larmour
2002-10-30 1:09 AL Chane
2002-10-30 4:52 ` Chris Garry
2002-04-10 18:23 [ECOS] Memory layout Agarwal, Lomesh
2002-04-10 18:18 Agarwal, Lomesh
2002-04-11 18:03 ` Jonathan Larmour
2002-04-10 15:31 Agarwal, Lomesh
2002-04-10 17:39 ` Jonathan Larmour
2002-04-10 14:01 Agarwal, Lomesh
2002-04-10 15:22 ` Jonathan Larmour
2002-04-07 16:14 Agarwal, Lomesh
2002-04-10 13:51 ` Jonathan Larmour
2001-01-23 22:51 [ECOS] memory layout Natarajan, Mekala (CTS)
2001-01-23 23:46 ` Jesper Skov
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.20010419184820.gthomas@cambridge.redhat.com \
--to=gthomas@cambridge.redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=james_ch1@sina.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).