public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Koco <ilijak@siva.com.mk>
To: Frank Pagliughi <fpagliughi@mindspring.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: Any shell available?
Date: Fri, 02 Jun 2006 16:19:00 -0000	[thread overview]
Message-ID: <4480651E.2050709@siva.com.mk> (raw)
In-Reply-To: <44805E04.2040400@mindspring.com>

Frank Pagliughi wrote:
> Ilija Koco wrote:
>
>> Zimman, Chris wrote:
>>
>>> We've actually written a small shell for eCos that we use internally.
>>> There's no objloader support for our platform yet (AFAIK), but we use
>>> something similar to the RedBoot_cmd() syntax to bring in commands to
>>> the shell.  There's a "ps" clone, mount/unmount for the filesystems, 
>>> ls,
>>> etc.
>>> There's no scripting support, but there's no reason it couldn't be
>>> added.
>>>
>>> If anyone is interested, let me know and I'll see if I can pack it up
>>> into something exportable.
>>>
>>>   
>>
>> Seems nice. I was about to suggest something like this. Maybe add 
>> some networking stuff like ping, ssh, ftp, etc (All 
>> selectable/configurable by menas of cdl).
>> Ilija
>>
> Having just finished a vxWorks project, I kind of miss their shell for 
> some quick debugging features. Theirs is not a Linux-style bash shell 
> or anything similar. Rather, it's a thread within the single target  
> process that acts like a C/C++ interpreter. The OS is loaded at 
> boot-up, but application modules can be dynamically loaded and 
> unloaded while the target is running.
That's the general idea a thread that executes some unix like commands.
>
> You can call indvidual functions at the command line. All stdout is 
> sent to the command line and when the function completes, the shell 
> reports the return value. Just like working with an interpreted 
> language. Then you can recompile just your module and reload it while 
> the target is still running.
>
> When done debugging, you can then compile the OS and app all together 
> in one executable (like eCos) without the debug & shell threads.
Or meybe leave a shell with only "non-debugging related" commands" ls, 
ps, ping.
>
> It's really handy for quick and dirty debugging.
>
> Frank
>
>
>


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

  parent reply	other threads:[~2006-06-02 16:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31 18:28 Zimman, Chris
2006-06-02 10:47 ` Ilija Koco
     [not found]   ` <44805E04.2040400@mindspring.com>
2006-06-02 16:19     ` Ilija Koco [this message]
     [not found] <3B530EF12E388B408ECC3162BA8C00F401BBE726@ny2526.corp.bloomberg. com>
     [not found] ` <3B530EF12E388B408ECC3162BA8C00F401BBE726@ny2526.corp.bloomberg .com>
2006-05-31 22:28   ` John Carter
  -- strict thread matches above, loose matches on Subject: below --
2006-05-31  1:02 Anthony Tonizzo
2006-05-31  8:37 ` Andrew Lunn
2006-05-31 11:51   ` Luis Friedrich
2006-05-31 12:20     ` Andrew Lunn
2006-05-31 16:42     ` Anthony Tonizzo
2006-05-31 21:47     ` David N. Welton

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=4480651E.2050709@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=fpagliughi@mindspring.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).