[okl4-developer] Fast and Optimized System StartUp / OKL4 in an automotive environment

[Josh Matthews]

Hi Oliver,

Welcome to OKL4.

On Thu, May 22, 2008 at 10:11 PM, Oliver Mayer-Buschmann <
omb at opensynergy.com> wrote:

>
> we consider to use OKL4 for our automotive platform.
> In an outomotive environment, you have strict requirements concerning
> startup and response times for electronic control units (ECU).
>
> So my first question to you is the following:
>
> Is it possible to divide the flash images (e.g. for ARM) in small
> pieces?
> We need a tiny and rapidly loadable image, containing the kernel + our
> basic software modules and drivers. It must be possible to reload
> further images (DMA??) on demand and to mount them into the file system
> on runtime. We'd like to use Iguana for our real time environment, so
> it's needed, that Iguana is able to reference software modules across
> these multiple flash images.


The microkernel approach of OKL4 will be most beneficial to achieving your
objective of a small and rapidly-loadable image. The OKL4 kernel can be
configured at build time (using the ElfWeaver tool) to construct only the
barest of functionality you require in your initial image; essentially, it
can be as small as you need. The partitioning approach would then involve
the construction of your other required functionality into servers, isolated
in their own protection domain, which could be demand-loaded from flash,
hdd, or a network device. This minimisation of your TCB has obvious other
benefits as well - in terms of complexity reduction, fault isolation, and
security - which I'd imagine are also strict requirements in your automotive
environment.

Best regards,
Josh Matthews
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20080523/9b916edd/attachment.htm