This is the mail archive of the
mailing list for the eCos project.
RE: Re: VxWorks type embedded "shell" for eCos
- From: "Robert Cragie" <rcc at jennic dot com>
- To: "Kelvin Lawson" <klawson at ad-holdings dot co dot uk>, <ecos-discuss at sources dot redhat dot com>
- Date: Fri, 6 Feb 2004 12:14:38 -0000
- Subject: RE: [ECOS] Re: VxWorks type embedded "shell" for eCos
Some work was done porting Lua to eCos. This is an small footprint,
embedded, extensible OO language with an example interactive shell.
The language could probably be extended to do the things you want and you
get a scripting environment too.
Robert Cragie, Design Engineer
Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK
http://www.jennic.com Tel: +44 (0) 114 281 2655
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com]On Behalf Of Kelvin
> Sent: 06 February 2004 10:08
> To: firstname.lastname@example.org
> Subject: [ECOS] Re: VxWorks type embedded "shell" for eCos
> Coming from a VxWorks background this is also something I miss. Because
> of this I wrote a similar shell for Nucleus in a previous job, so I may
> be able to help.
> My favourite feature was the ability to call C functions from the shell,
> and I liked having access to the symbol table. Good integration of the
> symbol table and shell is useful, so you can use symbol names instead of
> addresses in breakpoint calls, spawned C functions, setting variable
> values etc.
> Jeffrey R. Szczepanski wrote:
> > For people interested in a target debugger/shell capabilities
> under eCos:
> > The reason for my note here is to gauge interest in the set of
> > normally associated with the VxWorks target shell type functionality. I
> > would envision this as a new package for eCos that would allow users to
> > configure in a target debugger/shell that is driven from the
> > symbol table information. Some initial capabilities might include:
> > - calling arbitrary (public) C functions from the command line, with
> > arguments/symbols of choice
> > - lookup symbols in the symbol table
> > - spawn threads
> > - pause/resume threads
> > - dump memory, and edit memory locations
> > - list information about all runnning threads (dump the task table)
> > - Uses any configured stdin/stdout based device for I/O
> > - dump stacks, disassemble memory
> > - etc.
> > Searching the discussion group history there seemed to be some
> discussion on
> > this in the past - mixed opinions on the general need/desire for such a
> > capability to a wider audience. Personally, I think this would
> be a really
> > nice enhancement to the eCos enviroment if this evolved into a
> new package
> > that could be configured into an eCos build.
> > Point in fact, I have already implemented a basic version of
> several of the
> > above capabilities for my own use and am considering opening it
> up to the
> > community at large. So at this point, I am looking for feedback
> from people
> > (to the group or to me directly) about their interest in using such a
> > package and/or contributing to such a package.
> > Best Regards,
> > Jeff
> > =================================
> > Jeffrey R. Szczepanski, email@example.com
> > InSciTek Microsystems, Inc.
> > www.inscitek.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
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss