This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: eCos basic questions
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: mohanlal <mljangir at yahoo dot co dot in>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: 30 May 2003 10:55:47 +0100
- Subject: Re: [ECOS] eCos basic questions
- References: <20030528061006.50896.qmail@web8005.mail.in.yahoo.com>
mohanlal <mljangir@yahoo.co.in> writes:
> I am new to eCos and having some queries about eCos.
> Setup: I have two intel x86 machines. I am using one
> as developement and another as target. I have booted
> target machine from Redboot and have compiled Hello
> world program with eCos over developement machine.
> When I try to load a.out to target machine through
> gdb(from developement machine), I see "Hello world" in
> gdb console. Now my questions are as follow:
> 1. is eCos OS still running on target or has exited?
It is still running. Or rather, the main thread is simply in a tight
loop. There is no real concept of eCos exiting, since it is an
embedded OS, which shouldn't stop. We ususally get the effect of an
exit during development by planting a breakpoint in a suitable place.
> 2. Is there no concept like init process running
> continuously?
There is an idle thread. eCos does not have processes in the
Unix/Linux sense.
> 3. What if a function registers a packet handler for
> some protocol and exits? Will that handler be called
> when packet belonging to registered protocol is
> received?
>
Sure, why not?
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss