Re: [ECOS] OSEK compliance in eCos

[Fabian Scheler <fabian.scheler@gmail.com>]

Hi,

1.  As I already mentioned in a different thread, eCos is an operating
system usable also for hard real time systems.

2. When implement an OSEK compliance layer on top of eCos, how should
this eCos-based OSEK layer now be capable of doing hard real time? It
is still the same operating system kernel.

3. It might be quite hard to implement just an OSEK compliance layer.
You have to implement at least a different thread queue: the OSEK/VDX
standard demands that TASKs are activatanle several times and the
activation order has to be preserved. It might also get very tricky to
implement resources on ISR level and adopt the interrupt
synchronization mechanism.

4. The real strenght of OSEK based systems is, that you not just
configure the runtime system, like this is the case with eCos, but a
complete application. This makes it possible to generate an operating
system that perfectly suites the needs of an application (you might
wonder how many possiblities there are to optimize the implementation
of an operating system kernel, even if it is as simple as OSEK is).

Ciao, Fabian

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