Hi all
How many times has that happened 
I have a USB class driver that is working fine on some machines and not others and I am not sure why.
The driver installs correctly. The enumeration completes without issues. My test app connects to the driver ok. The app then call writefile to send a command to the target device. The driver gets the EvtDeviceIoWrite without issue but the data is not sent to the device and it never completes. On the others where it works, the write completes, the test app then calls readfile repeated without issue (tested to a few million reads).
I have used a software USB trace tool that shows the OUT arriving and being sent and then entering a pending state.
Can anyone provide any pointers of what might be going on, where to look or suggest anything to help.
Thanks
Veronica
An external usb analyzer would be a good idea. The software analyzers can’t
really show you what is happening between platform and device.
Mark Roddy
On Thu, Sep 9, 2010 at 5:48 PM, Veronica Merryfield <
xxxxx@shaw.ca> wrote:
Hi all
How many times has that happened
I have a USB class driver that is working fine on some machines and not
others and I am not sure why.
The driver installs correctly. The enumeration completes without issues. My
test app connects to the driver ok. The app then call writefile to send a
command to the target device. The driver gets the EvtDeviceIoWrite without
issue but the data is not sent to the device and it never completes. On the
others where it works, the write completes, the test app then calls readfile
repeated without issue (tested to a few million reads).
I have used a software USB trace tool that shows the OUT arriving and being
sent and then entering a pending state.
Can anyone provide any pointers of what might be going on, where to look or
suggest anything to help.
Thanks
Veronica
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
If the system is Win7, you can look at the events generated by the bus
drivers, among which there may or may not be a clue as to what’s going on.
http://blogs.msdn.com/b/usbcoreblog/archive/2009/12/04/etw-in-the-windows-7-usb-core-stack.aspx
http://blogs.msdn.com/usbcoreblog/archive/2009/12/21/answering-the-question-what-s-wrong-with-my-device-using-usb-etw.aspx
On 9/9/2010 2:48 PM, Veronica Merryfield wrote:
Hi all
How many times has that happened
I have a USB class driver that is working fine on some machines and not others and I am not sure why.
The driver installs correctly. The enumeration completes without issues. My test app connects to the driver ok. The app then call writefile to send a command to the target device. The driver gets the EvtDeviceIoWrite without issue but the data is not sent to the device and it never completes. On the others where it works, the write completes, the test app then calls readfile repeated without issue (tested to a few million reads).
I have used a software USB trace tool that shows the OUT arriving and being sent and then entering a pending state.
Can anyone provide any pointers of what might be going on, where to look or suggest anything to help.
Thanks
Veronica
Thanks for the various suggestions, on and off list.
I managed to get windbg running on one of the machines that wasn’t working and discovered I was getting a bogus extra end point in the configuration - endpoint 0xe1, packet size 0xfffc. It looks like I had an endpoint count of 3 instead of 2 left over from a previous change on the device. Odd that some ignored it and tripped up others.
Vrnc
On 2010-09-09, at 2:48 PM, Veronica Merryfield wrote:
Hi all
How many times has that happened
I have a USB class driver that is working fine on some machines and not others and I am not sure why.
The driver installs correctly. The enumeration completes without issues. My test app connects to the driver ok. The app then call writefile to send a command to the target device. The driver gets the EvtDeviceIoWrite without issue but the data is not sent to the device and it never completes. On the others where it works, the write completes, the test app then calls readfile repeated without issue (tested to a few million reads).
I have used a software USB trace tool that shows the OUT arriving and being sent and then entering a pending state.
Can anyone provide any pointers of what might be going on, where to look or suggest anything to help.
Thanks
Veronica
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer