[ECOS] Anyone have ported ecos onto microblaze?

[ECOS] Anyone have ported ecos onto microblaze?

[Tang Yi]

Hello everyone,

I would like to know if anyone has already ported ecos onto microblaze 
(Xilinx FPGA softcore).

Regards,
Yi Tang 



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

[ECOS] Any shell available?

[Tang Yi]

Hello everyone,

I want to enquire if there is any shell or command-line support for run-time 
development available for ecos. There might be some for the Linux 
compatibilty package, but what if I do not include the linux compatibility 
package?

Regards,

Yi Tang
ITEE School,
The University of Queensland 



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

Re: [ECOS] Any shell available?

[Gary Thomas]

On Fri, 2006-05-26 at 15:27 +1000, Tang Yi wrote:
> Hello everyone,
> 
> I want to enquire if there is any shell or command-line support for run-time 
> development available for ecos. There might be some for the Linux 
> compatibilty package, but what if I do not include the linux compatibility 
> package?

The idea of a "shell" doesn't really fit in with an embedded system.
eCos is built to serve a single application - tuned for whatever you
need.  It is expected that once this application is started, that's
what the system runs.

RedBoot, the "ROM" monitor, does allow for some interactive uses,
loading of applications, etc.

Can you explain more about what you wanted a shell for?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


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

Re: [ECOS] Any shell available?

[Tang Yi]

Hi Gary Thomas,

Thank you for replying me.

But I don't quite agree with you. Since some of the guys in our group is 
deeply involved in uclinux and from their point of view, a shell is quite 
important for embeded linux systems.

And it provide:

1. The ability to interact with the system in real-time. This is useful for 
checking the system status, experimenting, testing, copying files into the 
system, etc.

2. A lot of shells can also be used as a programming language (e.g. bash). 
The programs are usually quite simple (e.g. deciding what programs to run at 
system startup), but can also get quite complex.

Maybe your view is true for the traditional embedded systems, but for some 
fancy embedded systems nowadays, they do focus a lot on the interface 
between humans and machines.

And I found ecos provide an package which support the GUI interface of 
microwindows, maybe that's a good substite for simple shell. But I wonder 
whether all the targets support microwindows?

Regards,
Yi Tang

----- Original Message ----- 
From: "Gary Thomas" <gary@mlbassoc.com>
To: "Tang Yi" <yitang@itee.uq.edu.au>
Cc: <ecos-discuss@ecos.sourceware.org>
Sent: Friday, May 26, 2006 8:01 PM
Subject: Re: [ECOS] Any shell available?


> On Fri, 2006-05-26 at 15:27 +1000, Tang Yi wrote:
>> Hello everyone,
>>
>> I want to enquire if there is any shell or command-line support for 
>> run-time
>> development available for ecos. There might be some for the Linux
>> compatibilty package, but what if I do not include the linux 
>> compatibility
>> package?
>
> The idea of a "shell" doesn't really fit in with an embedded system.
> eCos is built to serve a single application - tuned for whatever you
> need.  It is expected that once this application is started, that's
> what the system runs.
>
> RedBoot, the "ROM" monitor, does allow for some interactive uses,
> loading of applications, etc.
>
> Can you explain more about what you wanted a shell for?
>
> -- 
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
>
>
> -- 
> 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

Re: [ECOS] Any shell available?

[Andrew Lunn]

On Mon, May 29, 2006 at 02:37:01PM +1000, Tang Yi wrote:
> Hi Gary Thomas,
> 
> Thank you for replying me.
> 
> But I don't quite agree with you. Since some of the guys in our group is 
> deeply involved in uclinux and from their point of view, a shell is quite 
> important for embeded linux systems.

eCos != linux

They have very differnet design goals.
 
> And it provide:
> 
> 1. The ability to interact with the system in real-time. This is useful for 
> checking the system status, experimenting, testing, copying files into the 
> system, etc.
> 
> 2. A lot of shells can also be used as a programming language (e.g. bash). 
> The programs are usually quite simple (e.g. deciding what programs to run 
> at system startup), but can also get quite complex.
> 
> Maybe your view is true for the traditional embedded systems, but for some 
> fancy embedded systems nowadays, they do focus a lot on the interface 
> between humans and machines.
> 
> And I found ecos provide an package which support the GUI interface of 
> microwindows, maybe that's a good substite for simple shell. But I wonder 
> whether all the targets support microwindows?

We should probably start by defining what a shell is!

A shell is a way of telling the system to load a program from
secondary storage and execute it. So a DOS Box is a shell, bash is a
shell, the Windows explorer is a shell. Shell scripts are just a
sequence of programs being loaded and executed under the control of a
text file.

Now eCos has no concept of loading a program from secondary storage
and executing it. It has no concept of a program. It has no concept of
a process. Without these concepts a shell is impossible. 

eCos has one application, defined at link time, which does everything
in the system.

What is possible is CLIs and GUIs to allow interaction with the
application.  Microwindows is a library which provides the
infrastructure to build a GUI into the application. It would also be
possible to write a library of functions for implementing CLIs in the
application.

             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