Re: Nesting interrupts with ARM core
From: Jeo (jeo_at_ky___BIG-FISH-LITTLE-FISH___bert.com)
Date: 02/25/05
- Next message: Henrik: "Trying to understand SDK generation..."
- Previous message: Rick Davis: "CE 5.0 and DRM10"
- In reply to: Jeo: "Re: Nesting interrupts with ARM core"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 25 Feb 2005 12:06:51 -0000
OK, I've figured it out and got it working now..
joe
"Jeo" <jeo@ky___BIG-FISH-LITTLE-FISH___bert.com ---Remove all fish> wrote in
message news:u35dMwxGFHA.3912@TK2MSFTNGP10.phx.gbl...
> The code i posted receives the interrupt, but also receives interrupts
> from the keyboard. I read the interrupt controoller to work out if it was
> suposed to be an interrupt for my app, and call
> InterruptDone(SYSINT_CHAIN) if it was not for my app.
>
> But then i just receive the same interrupt again, it never gets serviced
> my the keyboard any more.
>
>
> Im really pulling my hair out over this... 4 weeks to write an interupt
> driver is a bit much, and the boss is starting to ask questions !
>
>
>
>
>
> Joe
>
>
> "Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> wrote in message
> news:u3Ih3fqGFHA.1208@TK2MSFTNGP10.phx.gbl...
>> The ARM core has only a single interrupt vector. However virtually ALL
>> CPUs that have the ARM core have some sort of interrupt controller that
>> you can quickly read to determine the first level interrupt sources. (You
>> can call those IRQs) Normally the OEMInterruptHandler in the OAL will
>> read the interrupt controller to determine the highest priority pending
>> Interrupt request and return the SYSINTR_ ID for that device.
>>
>> --
>> Steve Maillet
>> EmbeddedFusion
>> www.EmbeddedFusion.com
>> smaillet at EmbeddedFusion dot com
>>
>>
>
>
- Next message: Henrik: "Trying to understand SDK generation..."
- Previous message: Rick Davis: "CE 5.0 and DRM10"
- In reply to: Jeo: "Re: Nesting interrupts with ARM core"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|