From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15356 invoked by alias); 1 Feb 2007 17:23:35 -0000 Received: (qmail 15339 invoked by uid 22791); 1 Feb 2007 17:23:34 -0000 X-Spam-Check-By: sourceware.org Received: from mail.comtechefdata.com (HELO gwguardian.comtechefdata.com) (206.223.8.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 01 Feb 2007 17:23:27 +0000 Received: from tempegw.comtechefdata.com (unverified [10.6.2.10]) by gwguardian.comtechefdata.com (Vircom SMTPRS 4.35.480.0) with ESMTP id for ; Thu, 1 Feb 2007 10:21:07 -0700 X-Modus-BlackList: 10.6.2.10=OK;htalanki@comtechefdata.com=OK X-Modus-RBL: 10.6.2.10=OK X-Modus-Trusted: 10.6.2.10=NO Received: from Tempe-MTA by tempegw.comtechefdata.com with Novell_GroupWise; Thu, 01 Feb 2007 10:20:31 -0700 Message-Id: <45C1BEDF0200001F0001759E@tempegw.comtechefdata.com> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Thu, 01 Feb 2007 17:23:00 -0000 From: "Harish Talanki" To: References: <20070130214625.GG22661@lunn.ch> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] In-built shell for Redboot X-SW-Source: 2007-02/txt/msg00013.txt.bz2 Yes, vxWorks does it, and its convinience for run-time debugging & examining of various tasks. Most of the time, we include debug symbols during development, and take them out completely for production. Having this form of shell environment make it easy to debug in runtime system, especially for networking apps. My thanks to everyone for your valuable suggestion. >>> "wang cui" 01/31/07 6:56 PM >>> I think he want to call function by name directly without a warpper of "RedBoot_cmd()" macro. Actually VxWorks provide this function. It strips all symbles from application image, then generate a source file contains all symbles, then add it into project and rebuild it. Then user can call all functions directly from VxWorks shell. However, I think Redboot style is good enough. But what I am thinking about is: Can we divide the shell functionality from Redboot and create a new package(suppose to be RedShell)? Because we always need a shell in application, and there are very many things have been implemented in Redboot. If so, we can reduce a lot of work in writing application shell. >From: Andrew Lunn >To: Harish Talanki >CC: ecos-discuss@ecos.sourceware.org >Subject: Re: [ECOS] In-built shell for Redboot >Date: Tue, 30 Jan 2007 22:46:25 +0100 > >On Tue, Jan 30, 2007 at 02:09:52PM -0700, Harish Talanki wrote: > > eCos Experts, > > Is there a way I can invoke a function call directly from the shell, > > with Redboot boot loader. > > > I want to add bunch of function calls to the code, and be able to > > directly invoke them from > > command line. Is there any package or configuration option I need to > > choose? > > > > Right now I keep adding new Redboot Commands, to get arround this. > >What is the difference between adding a redboot command and calling a >function? All a redboot command does is call a function. > > Andrew > >-- >Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos >and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > _________________________________________________________________ ???? MSN Explorer: http://explorer.msn.com/lccn/ -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss