public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: John Mills <john.m.mills@alum.mit.edu>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] General Q: Calling RedBoot CLI function from eCos app
Date: Wed, 30 May 2007 17:12:00 -0000	[thread overview]
Message-ID: <465DAE14.4030600@mlbassoc.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0705301148500.17544-100000@otter.localdomain>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Mills wrote:
> All -
> 
> I have an eCos app which is stored in FLASH, compressed, expanded into RAM 
> for execution. I'm using RedBoot[ROM] as my environment. I would like to 
> call the RedBoot CLI command "version" from my eCos app, then parse the 
> returned results.
> 
> 1. Is this possible, and
> 2. Where can I learn how to invoke the RedBoot function and to intercept 
> its output?

There is no [direct] support for calling RedBoot commands from eCos, sorry.

Just curious - what information are you interested in getting/parsing?  It
may be available some other way.

- --
- ------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGXa4TmaKbSsQGV8ARAjA7AJ9IzzmOg/KLZPz8OR7J58vKrc/ikQCfRQ6b
LcKC22AzwYuGTQUwEtPafaU=
=W/Vh
-----END PGP SIGNATURE-----

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-05-30 17:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 17:02 John Mills
2007-05-30 17:12 ` Gary Thomas [this message]
2007-05-30 17:16   ` Andrew Lunn
2007-05-30 17:20     ` Andrew Lunn
2007-05-30 17:58       ` John Mills
2007-05-30 19:18       ` John Mills
2007-05-30 21:00         ` Andrew Lunn
2007-05-30 21:06           ` John Mills
2007-05-30 21:41             ` Andrew Lunn
2007-05-31 15:01               ` [ECOS] eCos configuration question (was Re: [ECOS] General Q ...) John Mills
2007-05-31 15:19                 ` Gary Thomas
2007-05-31 15:21                   ` John Mills
2007-05-31 15:21                 ` [ECOS] " Andrew Lunn
2007-05-31 16:41                   ` Grant Edwards
2007-05-31 17:09                     ` [ECOS] Re: eCos configuration question Sergei Organov
2007-05-31 17:24                     ` [ECOS] Re: eCos configuration question (was Re: [ECOS] General Q ...) Paul D. DeRocco
2007-05-31 17:30                       ` Gary Thomas
2007-05-31 17:35                         ` Grant Edwards
2007-05-31 19:01                       ` Andrew Lunn
2007-05-31 17:18                 ` [ECOS] " Sergei Gavrikov
2007-06-01  8:10                   ` [ECOS] Re: eCos configuration question Daniel Néri
2007-06-01  9:04                     ` Sergei Gavrikov
2007-06-01 14:23                       ` Grant Edwards
2007-06-01 14:30                         ` Gary Thomas
2007-06-01 14:37                           ` Grant Edwards

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=465DAE14.4030600@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=john.m.mills@alum.mit.edu \
    /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).