| Author |
Topic |
|
|
nghia
36 Posts |
 Posted - 01 May 2003 : 12:06:23
|
Hi,
Our Hardware generates interrupt signal to the Bitsy Plus,
Which IRQ input of Bitsy Plus should we use ?
howto make a Bitsy Plus (CE.net version 4.12) ackknowledge
these interrupt ?
Thanks
Nghia |
|
|
ctacke
877 Posts |
Posted - 01 May 2003 : 16:22:09
|
Nghia,
Directly connecting to system hardware interupt lines is outlined in Topic 936. |
 |
|
|
nghia
36 Posts |
Posted - 02 May 2003 : 11:38:51
|
Chris,
In the ADSInterrupt class constructor two libraries (DLLs) are loading
bceddk.dll and coredll.dll.
I found only bceddk.dll in the \Windows directory and the coredll.dll does not exist.
Where can I get the coredll.dll file ?
Thanks.
Nghia.
|
|
|
|
ctacke
877 Posts |
Posted - 02 May 2003 : 11:44:42
|
| Coredll.dll exists on every CE device - it is where the kernel resides. It marked as hidden so it doesn't show up in any directory. |
|
|
|
akidder
1519 Posts |
Posted - 07 May 2003 : 11:38:20
|
| You might take a look at topic 46 for a couple ways to see how to locate hidden system dlls. |
|
|
|
nghia
36 Posts |
Posted - 16 May 2003 : 10:57:27
|
I try to run your sample "InterruptTest" on Bitsy-Plus then I have the following error message:
Loading bceddk.dll...0x83116918
Loading coredll.dll...0x831ff4d4
Binding APIs...
InterruptConnect =0x02761e20
InterruptDisconnect =0x02761e6c
InterruptInitialize =0x03f85228
InterruptDisable =0x03f85308
InterruptDone =0x03f852a0
---- Starting test ----
---- 5 minutes left in test ----
Connecting interrupt 75...0x00000017
Initializing interrupt...FAILED (87)
FAILED: Cannot initialize interrupt
Did I do something wrong ?
I only change the Bitsy Ext Irs to Bitsy Plus Ext Irq :
// connect the Bitsy EXT_IRQ1, rising edge
ADSInt.Connect(BITSY_PLUS_EXT_IRQ1, INTR_MODE_EDGE | INTR_MODE_NEGATIVE_LOGIC);
Nghia.
|
|
|
|
ctacke
877 Posts |
Posted - 20 May 2003 : 10:26:59
|
To update everyone, I spoke with Nghia today about what he is seeing. On the BitsyPlus, EXT_IRQ1 is used by the Ethernet chip, so it is unusable unless you have a CF personality board. In addition EXT_IRQ2 is used by the USB driver. I've added usage notes to the source download that details these and other details about using system interrupts.
|
|
|
|
nghia
36 Posts |
Posted - 23 May 2003 : 08:41:10
|
Thanks Chris,
It works.
Yours instruction and sample about external interrupt are helpful.
I disable USB driver and use /Ext_IRQ2 as an interrupt input,
it works.
I hope that we receive soon the new Windows CE image (4.14) to use the external IRQ3, else we loose the USB connection.
Thank again.
Nghia.
|
|
|
|
akidder
1519 Posts |
Posted - 23 May 2003 : 09:42:00
|
Hi Nghia. Try build Bitsy Plus build 4.13. I posted it on the Bitsy Plus CE build selector yesterday.
Cheers, Drew |
|
|
|
tbenisa
2 Posts |
Posted - 22 Mar 2005 : 15:15:17
|
I am using BitsyX rev B, C, and I am trying to use external interrupt IRQ3. I used your example, ADSInterrupt.cpp/h. I handed off an interrupt event handle to the driver, and in the thread function I wait for the event to be signaled from the driver. The driver does not capture the interrupt, and therefore, the event never happens, so I time out.
Is there any thing I need to do in the registry to enable IRQ3?
|
|
|
| |
Topic |
|
All Forums
Hardware
Interrupt on Bitsy Plus
Forum Locked
Printer Friendly