Programming Info D2XXPG31.pdf

More documents

Recommendations

Info

97 D2XX Programmer's Guidethe application can perform other processing. Eventually, the application checks the result of theoverlapped request by calling FT_W32_GetOverlappedResult 82 . The events that occurred andresulted in this function returning are stored in lpdwEvent.ExampleThis example shows how to write 128 bytes to the device using non-overlapped I/O.FT_HANDLE ftHandle; // setup by FT_W32_CreateFile for non-overlapped i/oDWORD dwEvents;if (FT_W32_WaitCommEvent(ftHandle, &dwEvents, NULL)); // FT_W32_WaitCommEvents OKelse; // FT_W32_WaitCommEvents failedThis example shows how to write 128 bytes to the device using overlapped I/O.FT_HANDLE ftHandle; // setup by FT_W32_CreateFile for overlapped i/oDWORD dwEvents;DWORD dwRes;OVERLAPPED osWait = { 0 };if (!FT_W32_WaitCommEvent(ftHandle, &dwEvents, &osWait)) {if (FT_W32_GetLastError(ftHandle == ERROR_IO_PENDING) {// wait is delayed so do some other stuff until ...if (!FT_W32_GetOverlappedResult(ftHandle, &osWait, &dwRes, FALSE)); // errorelse; // FT_W32_WaitCommEvent OK// Events that occurred are stored in dwEvents}}else {// FT_W32_WaitCommEvent OK// Events that occurred are stored in dwEvents}© Future Technology Devices International Ltd. 2005
Appendix986 AppendixThis section contains type definitions 99 of the functional parameters and return codes used in theD2XX programming interface. It also contains a copy of the current FTD2XX.H file 105 .© Future Technology Devices International Ltd. 2005
Page 1 and 2:
Future Technology DevicesInternatio
Page 4 and 5:
IIID2XX Programmer's Guide12 FT_W32
Page 6 and 7:
5 D2XX Programmer's Guide2 Classic
Page 8 and 9:
7 D2XX Programmer's Guide2.2 FT_Get
Page 10 and 11:
9 D2XX Programmer's GuideID. Indexe
Page 12 and 13:
11 D2XX Programmer's Guide2.4 FT_Op
Page 14 and 15:
13 D2XX Programmer's Guideif (ftSta
Page 16 and 17:
15 D2XX Programmer's Guide2.7 FT_Re
Page 18 and 19:
17 D2XX Programmer's Guide2.8 FT_Wr
Page 20 and 21:
19 D2XX Programmer's Guide2.10 FT_S
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
27 D2XX Programmer's Guide2.18 FT_G
Page 30 and 31:
29 D2XX Programmer's Guide2.20 FT_P
Page 32:
31 D2XX Programmer's Guide2.22 FT_G
Page 35 and 36:
Classic Interface Functions342.25 F
Page 37 and 38:
Classic Interface Functions36Someti
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Classic Interface Functions42NULL);
Page 45 and 46:
Page 47 and 48: Classic Interface Functions462.34 F
Page 49 and 50: Classic Interface Functions482.36 F
Page 51 and 52: Classic Interface Functions50// all
Page 53 and 54: Classic Interface Functions52This e
Page 55 and 56: EEPROM Programming Interface Functi
Page 67 and 68: Extended API Functions664.1 FT_GetL
Page 69 and 70: Extended API Functions684.3 FT_GetB
Page 71 and 72: Extended API Functions70if(ftStatus
Page 73 and 74: FT-Win32 API Functions725 FT-Win32
Page 75 and 76: FT-Win32 API Functions74ExamplesThe
Page 77 and 78: FT-Win32 API Functions765.3 FT_W32_
Page 79 and 80: FT-Win32 API Functions78}© Future
Page 81 and 82: FT-Win32 API Functions80overlapped
Page 89 and 90: FT-Win32 API Functions885.11 FT_W32
Page 97: FT-Win32 API Functions965.19 FT_W32
Page 101 and 102: Appendix100FT_DEVICE_UNKNOWN = 3FT_
Page 103 and 104: Appendix102char *SerialNumber;// "F
Page 105 and 106: Appendix104FTCOMSTAT (FT-Win32 Prog
Page 107 and 108: Appendix106typedef PVOID FT_HANDLE;
Page 109 and 110: Appendix108#define FT_EVENT_RXCHAR
Page 111 and 112: Appendix110FTD2XX_APIFT_STATUS WINA
Page 113 and 114: Appendix112//// structure to hold p
Page 115 and 116: Appendix114char *SerialNumber);FTD2
Page 117 and 118: Appendix116BOOL WINAPI FT_W32_Close
Page 119 and 120: Appendix118BOOL WINAPI FT_W32_GetCo
Page 121 and 122: Index 120Index- B -Baud Rate 19, 20
show all

Programming Info D2XXPG31.pdf

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?