From: "Matt Sartori" <msartori@hanoverdisplays.com>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Simple Redboot Q's
Date: Tue, 26 Jul 2005 10:16:00 -0000 [thread overview]
Message-ID: <F9885E669725F248A1F6DB9109FDD6793570E5@Molly.hanover.local> (raw)
Does an application that is loaded and run by Redboot have to be linked
against the eCos libraries?
The examples in the "Embedded Software Development with eCos" book
suggests that you do but, aside from adding much to the size of the
application, you may just wish to run something that completely takes
over the hardware until the next reset.
The Redboot documentation says that this is the way it works but doesn't
give any examples.
What provisions would be necessary to make this work (e.g.. you
obviously don't want your app to overwrite the rom area Redboot sits in)
and are there any examples of this out there?
m@
--------------------------------------------------------------------------------
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.
If you received this in error, please contact the sender or postmaster (postmaster@hanoverdisplays.com) and delete the material from any computer.
Although we routinely screen for viruses, addressees should check this e-mail and any attachment for viruses. We make no warranty as to absence of viruses in this e-mail or any attachments.
Our Company's email policy is to permit incidental personal use. If this email is of a personal nature, it must not be relied upon as expressing the views or opinions of the company.
Visit out website at www.hanoverdisplays.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-07-26 10:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 10:16 Matt Sartori [this message]
2005-07-26 11:05 ` Andrew Lunn
2005-07-26 13:08 ` Gary Thomas
2005-07-26 13:20 Matt Sartori
2005-07-26 13:28 ` Andrew Lunn
2005-07-26 13:28 ` Gary Thomas
2005-07-26 14:52 Matt Sartori
2005-07-26 14:59 ` Gary Thomas
2005-07-26 15:55 Matt Sartori
2005-07-26 16:30 ` Andrew Lunn
2005-07-26 17:03 Matt Sartori
2005-07-26 17:21 ` Andrew Lunn
2005-07-27 11:17 Matt Sartori
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=F9885E669725F248A1F6DB9109FDD6793570E5@Molly.hanover.local \
--to=msartori@hanoverdisplays.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).