PicoMod 4 GPIO

ATS26 · Aug 18th 2009

Hallo,

ich möchte gerne beim PicoMod4 (falsches Forum, aber einen eigenen Bereich gibt es noch nicht) die Digitalen IO Pins nutzen, die auf einen Interrupt reagieren sollen. Hierfür verwende ich den IOPin GPIO5.
Dafür habe ich die folgenden Registry eingefügt.

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\DIGITALIO]
"UseAsIOA"=0x4200
"IRQCfg0A"=0x200
"DataDirA"=0x4000
"Prefix"="DIO"
"Dll"="DIGIO.dll"
"Order"=0x97
"Index"=0x1
"Ioctl"=0x4
"Port"=0x1
"FriendlyName"="Digital I/O driver for PicoMOD4"

Mein Code lautet wie folgt:
digio.h

Code

#include <dio_sdk.h>

digio.cpp

Code

BOOL CDigIO::OnInitDialog()
...
/* Open the digitalio port */
HANDLE hDIO = CreateFile(_T("DIO1:"), GENERIC_WRITE|GENERIC_READ, 0,NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL );
if (hDIO == INVALID_HANDLE_VALUE)
{
AfxMessageBox(_T("Fehler! IO-Pins nicht gefunden."),0,0);
}
DWORD dwPort = 1;
if( dwPort != -1 )
{
if( -1 == SetFilePointer( hDIO, dwPort, NULL, FILE_BEGIN ) )
{
Afx;essageBoxf(" ERROR: Can't access port %d (Error=%d)\r\n", dwPort, GetLastError() );
return FALSE;
}
}
/*** WAITIRQ.dwPin = pin number to use as irq.
* I.e.: GPIO5 = PIN29 = IO09, dwPin must set to 9
* WAITIRQ.dwTimeout = Timeout in ms to wait for irq.
* Used for IOCTL_DIO_WAIT_IRQ.***/
WAITIRQ cWaitIrq;
cWaitIrq.dwPin = 9;
cWaitIrq.dwTimeout = 10000;
/* Request a sysintr */
DWORD dwSysIntr;
if(!DeviceIoControl(hDIO,IOCTL_DIO_REQUEST_SYSINTR, &cWaitIrq.dwPin, sizeof(DWORD), &dwSysIntr, sizeof(DWORD), NULL, NULL))
[b]return FALSE;[/b]
/* Wait for a sysintr */
DWORD dwWaitRes = -1; /* Return value that indicates the event result. WAIT_OBJECT_0, WAIT_ABANDONED, WAIT_TIMEOUT */
DeviceIoControl(hDIO,IOCTL_DIO_WAIT_IRQ, &cWaitIrq,sizeof(WAITIRQ), &dwWaitRes, sizeof(DWORD), NULL, NULL );
/* Close the digitalio port */
CloseHandle(hDIO);
return TRUE;
}

Display More

Das Problem ist, dass er immer beim Request ein FALSE zurück gibt. Leider weis ich nicht weiter. Können sie mir da weiter helfen?

PS: GetLastError() gibt die 50 raus: ERROR_NOT_SUPPORTED 50: The request is not supported...
PPS: Das mit der PicoMod3 mitgelieferte Programm: "USE_DIO" liefert den gleichen Fehler beim PicoMod4. Bei der PicoMod3 kommt es zu einem Fehler bei:
"InterruptInitialize( dwSysIntr,hIsrEvent, NULL, 0 )" mit Code 87 (Falscher Parameter)

[admin edit: Moved into newly created PicoMOD4 forum]

fs-support_MK · Aug 18th 2009

I am really sorry. There still is a bug in the PicoMOD Device Driver Documentation. On WindowsCE 6 based systems the IO-Control to registers an interrupt is IOCTL_DIO_REQUEST_IRQ instead of IOCTL_DIO_REQUEST_SYSINTR.

ATS26 · Aug 18th 2009

thx, this part works now. but there is still an error in my program:
i modified the exampleprogram: "dio_test" as follow:

.h

Code

#include <dio_sdk.h>
...
class CDigIO : public CDialog
{
...
public:
HANDLE hDIO;
HANDLE m_hIsrEvent;
DWORD m_dwSysIntr;
TCHAR chDevice[_MAX_PATH];
DWORD dwPort;
int count;
}

Display More

.cpp

Code

extern "C" BOOL InterruptInitialize(DWORD idInt, HANDLE hEvent, LPVOID pvData, DWORD cbData);
extern "C" VOID InterruptDone( DWORD idInt );
extern "C" VOID InterruptDisable( DWORD idInt );
#define SYSINTR_FIRMWARE (8+8)
#define SYSINTR_EXTIO (SYSINTR_FIRMWARE+16)
DWORD CMoGeKoDlg::SetThread()
{
int nRet=0;
dwPort = 1;
int i = 0;
m_hIsrEvent = INVALID_HANDLE_VALUE ;
m_hIsrEvent=CreateEvent( NULL, FALSE, FALSE, _T("ISR") );
DWORD dwIRQ = 9;
m_dwSysIntr=SYSINTR_EXTIO;
wcscpy( chDevice, _T("DIO1:") );
// Es wird nur Signalleitung 5 benötigt
// Open the port1.
hDIO = CreateFile (chDevice, // Pointer to the name of the port
GENERIC_READ|GENERIC_WRITE,
// Access (read-write) mode
0, // Share mode
NULL, // Pointer to the security attribute
OPEN_EXISTING,// How to open the serial port
0, // Port attributes
NULL); // Handle to port with attribute
// to copy
if( dwPort != -1 )
{
if( -1 == SetFilePointer( hDIO, dwPort, NULL, FILE_BEGIN ) )
{
ERRORMSG(1, (L"Error initializing interrupt, InitInterrupt() failed (%d)\n\r", GetLastError()));
nRet = -1;
return nRet;
}
}
if(!DeviceIoControl(hDIO, IOCTL_DIO_REQUEST_IRQ, &dwIRQ, sizeof(DWORD), &m_dwSysIntr, sizeof(DWORD), NULL, NULL ) )
{
ERRORMSG(1, (L"Error initializing interrupt, InitInterrupt() failed (%d)\n\r", GetLastError()));
nRet = -1;
return nRet;
}
/* connect IRQ with event and enable IRQ */
if (!InterruptInitialize( m_dwSysIntr,m_hIsrEvent, NULL, 0 ))
{
ERRORMSG(1, (L"Error initializing interrupt, InitInterrupt() failed (%d)\n\r", GetLastError()));
nRet = -1;
return nRet;
}
int y = 0;
DWORD dwReturn;
SetEvent(m_hIsrEvent);
unsigned char data;
DWORD dwBytesWrite = 1;
for (i=0; i<10000; i++)
{
dwReturn=WaitForSingleObject(m_hIsrEvent, 10000);
// Signal für Oszi. Zeigt die Geschwindigkeit der Interruptverarbeitung an
if(dwReturn==WAIT_OBJECT_0)
{
data = 64;
WriteFile(hDIO, &data, dwBytesWrite, &dwBytesWrite, NULL);
data = 0;
WriteFile(hDIO, &data, dwBytesWrite, &dwBytesWrite, NULL);
count++;
InterruptDone(m_dwSysIntr);
}
else
{
break;
}
}
InterruptDisable(m_dwSysIntr);
DeviceIoControl( hDIO, IOCTL_DIO_RELEASE_SYSINTR, &m_dwSysIntr, sizeof(DWORD), NULL, 0, NULL, NULL );
if(m_hIsrEvent!=INVALID_HANDLE_VALUE)
CloseHandle(m_hIsrEvent);
if(hDIO!=INVALID_HANDLE_VALUE)
CloseHandle(hDIO);
if(m_hIsrEvent!=INVALID_HANDLE_VALUE)
CloseHandle(m_hIsrEvent);
return nRet;
}

Display More

Now the "InterruptInitialize(...)" function returns an error:
Error initializing interrupt, InitInterrupt() failed (87)

Any ideas?

ATS26 · Aug 18th 2009

do i need some additional .dll files? or .h files?

ATS26 · Aug 20th 2009

no more ideas?

fs-support_MK · Aug 20th 2009

The InterruptInitialize() function is no more available on WindowsCE 6. This by the way is the same reason that the IOCTL_DIO_REQUEST_SYSINTR Io-Control is no more usable on CE 6. On CE6 the principle operation is as follows:

1. Initialize the interrupt at the DIO driver: IOCTL_DIO_REQUEST_IRQ (replaces IOCTL_DIO_REQUEST_SYSINTR)
2. Afterwards you can wait for the interrupt event with IOCTL_DIO_WAIT_IRQ (replaces WaitForSingeObject())
3. To re-enable the DIO-Interrupt you must call IOCTL_DIO_INTDONE_IRQ (replaces InterruptDone())
4. To unregister and release the interrupt you may call IOCTL_DIO_RELEASE_IRQ (replaces IOCTL_DIO_RELEASE_SYSINTR) before exiting your programm.

This mechanism is documented correctly in the PicoMOD3 Device Driver Documentation. Only the IO-controls IOCTL_DIO_REQUEST_SYSINTR and IOCTL_DIO_RELEASE_SYSINTR values must be replaced with the new one. We will correct this and clearify the differences to the "old" interface used on Windows CE 5.

ATS26 · Sep 1st 2009

Hallo, i have still a problem with my DIO pins. Nothing still happends when i try to rise my DIO pin. My code looks as follows:

Code

DWORD CDIO::SetThread()
{
int tmp = 0
while(tmp = 0)
{
int nRet=-1;
/* Open the digitalio port */
HANDLE hDIO = CreateFile(_T("DIO1:"), GENERIC_WRITE|GENERIC_READ, 0, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
if( hDIO == INVALID_HANDLE_VALUE )
{
MessageBox(TEXT("WinMain(): CreateFile() failed"),TEXT("Err! Ã¢â‚¬â€œ DIO-Test"), MB_OK );
return nRet;
}
LONG lDistance = 1;
SetFilePointer( hDIO, lDistance, NULL, FILE_BEGIN);
/*
* WAITIRQ.dwPin = pin number to use as irq.
* I.e.: GPIO2 = PIN44 = IO15, dwPin must set to 15
* I.e.: GPIO1 = PIN41 = IO14, dwPin must set to 14
* WAITIRQ.dwTimeout = Timeout in ms to wait for irq.
* Used for IOCTL_DIO_WAIT_IRQ.
*/
WAITIRQ cWaitIrq[2];
cWaitIrq[0].dwPin = 15;
cWaitIrq[0].dwTimeout = 20000;
cWaitIrq[1].dwPin = 14;
cWaitIrq[1].dwTimeout = 20000;
/* Request a sysintr */
DeviceIoControl(hDIO,IOCTL_DIO_REQUEST_IRQ, &cWaitIrq[0].dwPin, sizeof(DWORD), NULL, 0, NULL, NULL);
/* Wait for a sysintr */
DWORD dwWaitRes = -1; /* Return value that
* indicates the event result.
* WAIT_OBJECT_0,
* WAIT_ABANDONED,
* WAIT_TIMEOUT */
DeviceIoControl(hDIO,IOCTL_DIO_WAIT_IRQ, &cWaitIrq[0], sizeof(WAITIRQ), &dwWaitRes, sizeof(DWORD), NULL, NULL );
if (dwWaitRes != -1)
{
tmp = 1;
}
/* Call InterruptDone on a sysintr */
DeviceIoControl(hDIO,IOCTL_DIO_DONE_IRQ, &cWaitIrq[0].dwPin, sizeof(DWORD), NULL, 0, NULL, NULL );
/* Release a sysintr */
DeviceIoControl(hDIO,IOCTL_DIO_RELEASE_IRQ, &cWaitIrq[0].dwPin, sizeof(DWORD), NULL, 0, NULL, NULL );
/* Close the digitalio port */
CloseHandle(hDIO);
return nRet;
}
}

Display More

my registry entries looks as follows:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\DIGITALIO]
"UseAsIOA"=0x8000
"IRQCfg2A"=0x0
"IRQCfg1A"=0x0
"IRQCfg0A"=0x1
"DataDirA"=0x0
"Prefix"="DIO"
"Dll"="PM4_DIGIO.dll"
"Order"=0x97
"Index"=0x1
"Ioctl"=0x4
"Port"=0x1
"FriendlyName"="Digital I/O driver for PicoMOD4"

My program should use the pins GPIO2 (and GPIO1) as input-pin. When i will set the PIN44 (J5 I/O Pin5 [and J5 I/O Pin16 to GND]) to high (3,3V), an interrupt should appear.

thx for your answers

ATS26 · Sep 1st 2009

so, now it works. i changed my reg settings to:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\DIGITALIO]
"UseAsIOA"=0x8000
"IRQCfg2A"=0x8000
"IRQCfg1A"=0x0
"IRQCfg0A"=0x8000
"DataDirA"=0x0
"Prefix"="DIO"
"Dll"="PM4_DIGIO.dll"
"Order"=0x97
"Index"=0x1
"Ioctl"=0x4
"Port"=0x1
"FriendlyName"="Digital I/O driver for PicoMOD4"

I think the problem was, that the rising edge time was too large.

ATS26 · Sep 3rd 2009

Hallo, my interrupt problem is still there. I tried to enable the GPIO1 and GPIO2. Therefore i changed the reg settings to:

"UseAsIOA"=0xC000
"IRQCfg2A"=0xC000
"IRQCfg1A"=0x0
"IRQCfg0A"=0xC000

(Bit IO15 and IO14 to 1)

The code looks as follows:

Code

/* Open the digitalio port */
HANDLE hDIO = CreateFile(_T("DIO1:"), GENERIC_WRITE|GENERIC_READ, 0, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL );
//Add error handling here
LONG lDistance = 1;
SetFilePointer( hDIO, lDistance, NULL, FILE_BEGIN);
/*
* WAITIRQ.dwPin = pin number to use as irq.
* I.e.: GPIO1 = PIN41 = IO14, dwPin must set to 14
* I.e.: GPIO2 = PIN44 = IO15, dwPin must set to 15
* WAITIRQ.dwTimeout = Timeout in ms to wait for irq.
* Used for IOCTL_DIO_WAIT_IRQ.
*/
WAITIRQ cWaitIrq[2];
cWaitIrq[0].dwPin = 15;
cWaitIrq[0].dwTimeout = 100;
cWaitIrq[1].dwPin = 14;
cWaitIrq[1].dwTimeout = 100;
/* Request a sysintr */
DeviceIoControl(hDIO,IOCTL_DIO_REQUEST_IRQ, &cWaitIrq[0].dwPin, sizeof(DWORD), NULL, 0, NULL, NULL);
/* Wait for a sysintr */
DWORD dwWaitRes = -1;
/* Return value that indicates the event result. WAIT_OBJECT_0, WAIT_ABANDONED, WAIT_TIMEOUT */
DeviceIoControl(hDIO,IOCTL_DIO_WAIT_IRQ, &cWaitIrq[0], sizeof(WAITIRQ), &dwWaitRes, sizeof(DWORD), NULL, NULL );
if(dwWaitRes == 0)
{
//Do something 1
}
/* Call InterruptDone on a sysintr */
DeviceIoControl(hDIO,IOCTL_DIO_DONE_IRQ, &cWaitIrq[0].dwPin, sizeof(DWORD), NULL, 0, NULL, NULL );
/* Release a sysintr */
DeviceIoControl(hDIO,IOCTL_DIO_RELEASE_IRQ, &cWaitIrq[0].dwPin, sizeof(DWORD), NULL, 0, NULL, NULL );
/* Request a sysintr */
DeviceIoControl(hDIO,IOCTL_DIO_REQUEST_IRQ, &cWaitIrq[1].dwPin, sizeof(DWORD), NULL, 0, NULL, NULL);
/* Wait for a sysintr */
DWORD dwWaitRes2 = -1;
/* Return value that indicates the event result. WAIT_OBJECT_0, WAIT_ABANDONED, WAIT_TIMEOUT */
DeviceIoControl(hDIO,IOCTL_DIO_WAIT_IRQ, &cWaitIrq[1], sizeof(WAITIRQ), &dwWaitRes2, sizeof(DWORD), NULL, NULL );
if(dwWaitRes2 == 0)
{
//Do something 2
}
/* Call InterruptDone on a sysintr */
DeviceIoControl(hDIO,IOCTL_DIO_DONE_IRQ, &cWaitIrq[1].dwPin, sizeof(DWORD), NULL, 0, NULL, NULL );
/* Release a sysintr */
DeviceIoControl(hDIO,IOCTL_DIO_RELEASE_IRQ, &cWaitIrq[1].dwPin, sizeof(DWORD), NULL, 0, NULL, NULL );
CloseHandle(hDIO);

Display More

Now my problem: This works just sometimes! Sometimes everything works great. Sometimes nothing works, that is no interrrupt is set and the function GetLastError() returns an invalid handler. Sometimes one Pin works, the other not. In most cases the PIN44 (J5 Starterkit Pin5) works and Pin41 (J5 Starterkit Pin1) doesn't work. After restart of this program the result is changing. After all i tried the debug and the release mode.
When i get the voltage at this pins, i get always 2V at PIN44 when my display is insert. That is the reason, why the GPIO2 often set the interrupt.

I'm using the PicoMOD Device Drivers Version 1.4 Date: 2009-06-15 and the PicoMOD3-Startinterface Hardware Version 0.10 Date 7.5.2008, but for my PicoMod4. Are there maybe changes in the position of the GPIO pins? Must there be always a closed electric circuit between the GPIO pins and the GND pin or is it enough, when i just contact the GPIO pin? (I tried both without any differece).

Share