Re: Bug in OHCI2 driver for Windows CE 5.0?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

About the zero-byte control transfer. The USB stack does send zero-byte
transaction as you said, we saw that in our USB logger.
What I meant was I cannot use this feature with the IssueVendorTransfer
API. Whenever I put a zero-length or/and null-pointer buffer the method
failed before the USB stack sends the command down to the root-hub.

About the CE's USB stack: The hardware ends the transaction (We saw it
in the USB logger), but the SHORT_TRANSFER_OK flag, as you said doesn't
work with this praticular stack implementation. When I saied the
SHORT_TRANSFER_OK doesn't work was the following:
- Our device send the information and close the transaction (We can
verify that using a simple logger, and we did)
- The driver (invoking the IssueVendorTransfer with SHORT_TRANSFER_OK)
doesn't get any result from the USB stack and keep waiting
- A timeout occured, and the USB return faliure code.
- The buffer for the TD description doens't contains ANY information
sent by the device.
We cannot change the firmware itself since its operational over
thousands of users.
We must make the USB stack to work.

Thanks for the reply.
Elad.

.