Hello
Is there any specific reason why trace output generated with printf() or similar functions is not routed to OKL4's KDB interface (functions L4_KDB...)? Instead in file okl4_console.cc a direct access to COM1's hardware registers is implemented. This creates the problem that there is a concurrency access to the hardware by the OKL4 kernel and any Genode-based application. In my case it is even worth, because I deal with a hardware which does not provide a legacy COM port. I have adapted the KDB to the specific hardware, so any application using the KDB interface would benefit from it. But Gernode ignoring it makes it unrunnable on this special platform. Since the problem is urgent, I require some hints to make Genode able using OKL4's KDB interface.
Regards Frank
Hello Frank,
On Thu, Jul 30, 2009 at 01:37:22PM +0100, Frank Kaiser wrote:
Is there any specific reason why trace output generated with printf() or similar functions is not routed to OKL4's KDB interface (functions L4_KDB...)?
AFAIK we had minor issues with scheduling (switch_to) and the OKL4 debug console during first steps of our port. You may adapt okl4_console.cc easily to use the build-in kernel debugger if that is okay for you.
Since the problem is urgent, I require some hints to make Genode able using OKL4's KDB interface.
Please have a look into
base-pistachio/src/base/console/pistachio_console.cc
I expect the OKL4 solution will look similar.
Greets
Hello, Christian
Thanks for the response. Meanwhile I've managed to attach the Genode console to the OKL4 KDB interface. It was a bit tricky to get the necessary OKL4 C header files together so that the interface got compiled in Genode's C++ context, but then it worked immediately. Output to the non-legacy UART also works.
Frank
-----Original Message----- From: Christian Helmuth [mailto:christian.helmuth@...1...] Sent: Thursday, July 30, 2009 4:24 PM To: genode-main@lists.sourceforge.net Subject: Re: Tracing with Genode on OKL4
Hello Frank,
On Thu, Jul 30, 2009 at 01:37:22PM +0100, Frank Kaiser wrote:
Is there any specific reason why trace output generated with printf() or similar functions is not routed to OKL4's KDB interface (functions L4_KDB...)?
AFAIK we had minor issues with scheduling (switch_to) and the OKL4 debug console during first steps of our port. You may adapt okl4_console.cc easily to use the build-in kernel debugger if that is okay for you.
Since the problem is urgent, I require some hints to make Genode able using OKL4's KDB interface.
Please have a look into
base-pistachio/src/base/console/pistachio_console.cc
I expect the OKL4 solution will look similar.
Greets
Christian Helmuth Genode Labs
http://www.genode-labs.com/ · http://genode.org/
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
-
Christian Helmuth -
Frank Kaiser