[okl4-developer] OKL4 2.1: Build Option 'VEBOSE_INIT=1 ' does not work
Geoffrey Lee
glee at ok-labs.com
Mon Jun 23 12:44:25 EST 2008
On Fri, Jun 20, 2008 at 11:16:41AM +0200, Frank Kaiser wrote:
> Hello
Hi Frank
I've been told by the kernel guys that the issue you see should
have been addressed some time ago. Can you let us know which version
of OKL4 you are using, what machine you are building for and
if possible re-test with the latest version to confirm that the
problem has gone away?
-gl
>
>
>
> 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.
>
--
More information about the Developer
mailing list