IssueInterruptTransfer

This function initiates an interrupt transfer with a USB device on the specified endpoint.

USB_TRANSFER IssueInterruptTransfer(
  USB_PIPE hPipe,
  LPTRANSFER_NOTIFY_ROUTINE lpStartAddress,
  LPVOID lpvNotifyParameter,
  DWORD dwFlags,
  DWORD dwBufferSize,
  LPVOID lpvBuffer,
  ULONG uBufferPhysicalAddress 
);

Parameters

• hPipe
  [in] Handle to an open USB pipe.
• lpStartAddress
  [in] Pointer to the address of a callback routine, or NULL if no callback routine is necessary
• lpvNotifyParameter
  [in] Parameter to pass to the callback routine.
• dwFlags
  [in] Flags for the transfer. These flags shown in the following list are declared in the Usbtypes.h header file.
  • USB_IN_TRANSFER
  • USB_OUT_TRANSFER
  • USB_NO_WAIT
  • USB_SHORT_TRANSFER_OK
  • USB_START_ISOCH_ASAP
  • USB_COMPRESS_ISOCH
  • USB_SEND_TO_DEVICE
  • USB_SEND_TO_INTERFACE
  • USB_SEND_TO_ENDPOINT
  • USB_DONT_BLOCK_FOR_MEM
• dwBufferSize
  [in] Size of data buffer.
• lpvBuffer
  [in] Pointer to the data buffer. If the physical buffer address is specified, this must contain the virtual address of the buffer.
• uBufferPhysicalAddress
  [in] Physical address, which may be NULL, of the data buffer.

Return Values

A USB_TRANSFER handle indicates success. NULL indicates failure. IssueControlTransfer behaves either synchronously or asynchronously, depending on the value you provide for lpStartAddress and whether dwFlags contains the USB_NO_WAIT flag. The following table shows the possible flags.

When behaving asynchronously, the function invokes your callback function, if lpStartAddress specifies one, when the transfer is complete.

Requirements

OS Versions: Windows CE 2.10 and later.
Header: Usbd.hpp.

See Also

AbortTransfer | GetTransferStatus | IsTransferComplete | USB Drivers

 Last updated on Tuesday, May 18, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.