[wdmaudiodev] Re: Can I view the debug messages from Windows USB drivers?
- From: Tim Roberts <timr@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Thu, 04 Nov 2004 14:33:33 -0800
Liang Shiyi wrote:
I'm writing USB audio device (microphone) firmware, I want to use the USB audio
class driver instead of rewriting another one on my own.
Now, the device can respond to the requests issued by the host. But it just fails after URB_FUNCTION_SELECT_CONFIGURATION with the result code 0xc0000004 (by viewing the log file of SniffUSB.exe). I doubt there's something incorrect inside the descriptors, but I can't tell, I just copy those decriptors from the USB audio spec "audio10.pdf".
I don't think that's a descriptor problem. C0000004 is
USBD_STATUS_STALL_PID; now, I'm not 100% sure what that means, exactly,
but the fact that it stalls implies that your firmware did not respond
correctly to the SELECT_CONFIGURATION request.
Do you have a USB protocol analyzer, like a CATC?
Who can tell me how to debug the firmware with Window 2k/XP?
Debugging firmware usually requires an oscilloscope and a protocol
analyzer. What is your base device? Are you using one of the Cypress
USB chips?
Can I view the debug messages from the built-in USB drivers? and how?
Have you tried installing the checked build of XP?
--
- Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
Other related posts:
