<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=DE link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hello<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-US>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 <a href="http://www.ertos.nicta.com.au/software/kenge/">http://www.ertos.nicta.com.au/software/kenge/</a>
as many other features), but found it causing a crash. The reason is that this
option activates the macro <b>TRACE_INIT()</b> which tries to make formatted
output to the kernel console thru function <b>printf()</b>. The point is that the
kernel memory intialisation <b>kmem_t::init()</b> uses this trace macro, and
the memory initialisation is called before <b>Platform::init()</b> (which is
responsible for mapping the IO address space needed by the kernel) and <b>init_console()</b>
(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.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US>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 <b>init_hello()</b>.
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.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Regards<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Frank<o:p></o:p></span></p>
</div>
</body>
</html>