[okl4-developer] regarding interrupts
Gabi Voiculescu
boy3dfx2 at yahoo.com
Mon Apr 21 15:06:13 EST 2008
Hello again.
Thanks for the advice on the entering kdb. Your advices helped me to rule out a set of causes for the freeze and pointed me to debug the kernel timer driver.
After I resolved the timer problems I have been able to enter kdb from the console.
Test_libs=all runs with 99% success. The only miss is at
libs/iguana/test/memsect_tests.c:235:F:Memory Sections:MEMS0600: Unable to create and direct section.
Max_memsections is 0.
Is this an error? Any thoughts on what can cause this error? I should say I have mapped 128MB of RAM.
Beside this I have a couple more questions for you. I would appreciate even partial answers to these.
1 - in platform/..../plat.cc in OKL4 1.5.2 I have defined a vector called arm_bootdesc which I see defines non RAM areas for the particular platform. What is it's purpose?
1a - If I use the reserved type can I impose restrictions on a memory area - say flash?
1b - Do I define RAM sections in there?
1c - Is there a particular order in which the entries have to be declared? For example in every example platform except for one the areas are defined in incremental order.
2 - Is there a way to get rid of the v1 driver information in platform/..../tools/machines.py, and still have the build create a good image?
Currently, on okl4-1.5.2, if I comment out the lines
timer_driver = "arm1176_timer"
serial_driver = "drv_l4_kdb"
drivers = [timer_driver, serial_driver]
I get two warning messages in the beginning of the build, and more importantly, I can no longer enter in okl4 (program halts somewhere in init_tracebuffer() ). My only concern would be if there is a conflict between the v1 and v2 drivers (currently I specify different drivers for the kdb serial) that the test_libs don't pick up.
Thanks for your support so far,
Gabi Voiculescu
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20080420/c6545136/attachment.htm
More information about the Developer
mailing list