[okl4-developer] iguana fails to start on a new platform

[Gabi Voiculescu]

This problem is due to not assinging irqs above 34 to iguana server in the build script: cells/iguana/SConscript.

On my hardware platform the irqs were in the 32-64 range.

I made an assign_irq entry for my platform (thus not going to the default else branch in the python script) and now I go beyond this problem, finalizing the iguana initialization.

Gabi Voiculescu

--- On Thu, 7/30/09, Gabi Voiculescu <boy3dfx2 at yahoo.com> wrote:

From: Gabi Voiculescu <boy3dfx2 at yahoo.com>
Subject: [okl4-developer] iguana fails to start on a new platform
To: developer at okl4.org
Date: Thursday, July 30, 2009, 6:00 PM

Hello.

I am trying to verify the port of the v2 drivers by running an iguana lcd example.

I know how outdated is iguana from okl4 3's perspective, but I still want to see this port run.

This example begins my iguana example for gumstix (armv5) but fails to reach the example begin stage for my armv6 platform (macro ARCH_VER == 6):

--------- output using DEBUG_TRACE=5 in my platform -------------------
GRANT INTERRUPT (tid: 44, irq: 41)             
bounce interrupt failed
 41                                                                                           
iguana/server/src/bootinfo.c:1323 grant_interrupt: Record 427: Cannot register interrupt. 
--- KD# User: PANIC: Bootinfo did not initialise correctly ---   

This happens for the first GRANT INTERRUPT process.

As I see the bootinfo source tries to revoke the interrupt from it's implicit space (iguana) and then tries to grant the interrupt to the vserver space (vtimer for v2 timer driver,
 vserial for v2 serial driver). This is done in two steps: calling soc_security_control_interrupt().

I see no obvious weaver.xml syntax cap differences between the two platforms involving this first interrupt.
I'm not sure if in order to grant initially the v2 driver's timer interrupt to iguana I need to look for the cause in the build script or in the iguana server initialization C code.
I would appreciate ideas from anybody who had this kind of problem before.

Thank you,
Gabi Voiculescu 







      
-----Inline Attachment Follows-----

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



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20090730/d6cc1716/attachment.htm