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

[Geoffrey Lee]

On Thu, Oct 09, 2008 at 11:41:02PM +0200, Oliver Mayer-Buschmann wrote:
> Hi,
> 

Hi Oliver - I am guessing you intend for these packages to be 
loaded dynamically at run-time on demand, and hence these modules
should live outside of the main bootable image.  In this case
rather than putting it into the bootinfo, maybe you can
create a package manager that "knows" about all the packages
available on a given system and let it load these packages
directly on demand?  Off the top of my head I don't recall
anything special that you might have to do if you were 
to run a program dynamically, other than go through the 
standardized Iguana application pd creation and thread creation.
In the case of dynamically loaded programs you'd probably create
a memory section(s) and load your ELF load your program into those 
memory section (s).

	-gl

> I'd appreciate to receive some feedback and information from you.
> 
> As explained in this tread:
> http://wiki.ok-labs.com/forum?query=startup%20automotive
> I'm working on an modularized startup concept for Iguana.
> 
> At this point I've finished all basic work to start with my package  
> loader implementation.
> 
> A package is a set of iguana applications (e.g. a package contains 1  
> or more iguana servers or a wombat).
> Let's say, a package is an ELF-File (e.g. one of the ELF-Files from / 
> build/iguana/bin)
> 
> I have acces to NAND and I've integrated YAFFS2 to L4, so I'm able to  
> load ELF-files to RAM,
> using the NICTA ELF-loader.
> 
> The last missing step to prove the concept, is to register the  
> additional loaded programs to iguana.
> 
> I've had a first deeper look into the bootinfo parsing of the iguana  
> server.
> Hmm, ... I'm able to use gdb in skyeye ... one of how many @TODOs in  
> OKL ^^
> anyway ...
> 
> I can imagine some different possibilities to implement the  
> registration to iguana, e.g.:
> 
> 1. I could define my own iguana registration meta data (e.g. in XML),  
> implement a separate iguana server
> and use the ig_server idl4 API to create memsections, pds, etc and  
> register the package to L4.
> Any hint's in using the iguana API is appreciated-I'm talking about  
> semantic! ;-)
> 
> 2. I could modify elfweaver to be able to create (merge) packages for  
> me that contain the needed bootinfo section
> to be parsed inside the iguana root server . The elfweaver manual  
> tells me, that I can bring additional code to ig_server,
> using elfweaver's extension feature. Has anybody tested or used this?
> Can somebody help me with elfweaver modifications?
> Where is the best starting point in creating ELF-files with bootinfos,  
> that do not contain a root server nor a kernel but references to
> programs, that only exist in other packages? Any useful information is  
> definitely appreciated!
> 
> Thanks!
> 
> Oliver
> 
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
> 

--