Re: InterruptInitialize fails
- From: shai <shaihi@xxxxxxxxx>
- Date: Thu, 13 Nov 2008 00:43:07 -0800 (PST)
Hi,
Might be that your Event Handle is not good.
look at this post:
http://groups.google.com/group/microsoft.public.windowsce.embedded/browse_thread/thread/77f1bc12020fa5f2
Shai
On Nov 12, 9:08 pm, "BhavinShah" <u47534@uwe> wrote:
Hi,
I am trying to port a CE5.0 based driver that the previous engineer created
to CE 6.0 and having issues with InterruptInitialize failing!!
The driver design seems very strange to me as it is existing. I do not see
any driver entry points like DRV_Init , DRV_DeInit etc. It seems to be just a
linked DLL with an export symbol. Since the entry points are not present, the
driver load using udevice.exe fails. When I start my application that uses
the driver, the driver loads and when it tries to do an InterruptInitialize,
I get an error code of 0x57 ( invalid parameter ).
I am using IRQ5 for the board. I do not need any special ISR so the default
implementation of PeRPISR should be sufficient. Am I correct ?
I would really appreciate any help on this issue.
Thanks in advance,
Bhavin
.
- Follow-Ups:
- Re: InterruptInitialize fails
- From: BhavinShah via PocketPCJunkies.com
- Re: InterruptInitialize fails
- References:
- InterruptInitialize fails
- From: BhavinShah
- InterruptInitialize fails
- Prev by Date: Re: Physical memory access from C# in WinCE 6.0
- Next by Date: Re: Physical memory access from C# in WinCE 6.0
- Previous by thread: InterruptInitialize fails
- Next by thread: Re: InterruptInitialize fails
- Index(es):
Relevant Pages
|