[okl4-developer] OKL4 2.1: Build Option 'VEBOSE_INIT=1 ' does not work

[Geoffrey Lee]

On Fri, Jun 20, 2008 at 11:16:41AM +0200, Frank Kaiser wrote:


Hi Frank

> Hello
> 
>  
> 
> I am currently trying to adapt OKL4 to another ARM9 platform which is ATMEL AT91SAM9263. To get more debug information during the startup phase I tried the build option 'VERBOSE_INIT=1' (derived from the content of 'pistachio/SConscript', but undocumented at http://www.ertos.nicta.com.au/software/kenge/ as many other features), but found it causing a crash. The reason is that this option activates the macro TRACE_INIT() which tries to make formatted output to the kernel console thru function printf(). The point is that the kernel memory intialisation kmem_t::init() uses this trace macro, and the memory initialisation is called before Platform::init() (which is responsible for mapping the IO address space needed by the kernel) and init_console() (which initialises the serial port for kernel messages) are called. Trying to output to the console's virtual address while this address is not yet mapped to the physical address leads to the crash.


Thanks for catching that.  I will track this in our bug database.



> 
> Possibly there are other functions trying to write to the console before it is initialised, so I stopped using 'VERBOSE_INIT=1' and voilà: I got the kernel startup message provided by init_hello(). Can anyone describe which of many build options found in 'pistachio/SConscript' are valid? At least the description of the Kenge build system found on the already mentioned website is quite brief considering the complexity of this composition of SCONS acripts and multiple PYTHON scripts.



There are indeed quite a number of user-settable options in the
pistachio/Sconstruct.  Is there some option that you are 
particularly after?

	-gl


> 
>  
> 
> Regards
> 
> Frank
> 

> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer


--