|
Message
From: Trainee IAC, (IE10)<trainee.iac@h...>
Date: Mon Oct 11 11:11:29 CEST 2004
Subject: [usb] bulkusb.sys with usb1_funct and usb_phy
hi matt,
i feel the baud rate at which u are trying to communicate with device may
be not right. jst check what baud rate the device supports and do reply me
if there is any progress.
thanks and regards
paul
> -----Original Message-----
> From: usb-bounces@o... [mailto:usb-bounces@o...]
> On Behalf Of Matt Gillespie
> Sent: Monday, October 11, 2004 1:22 AM
> To: usb@o...
> Subject: [usb] bulkusb.sys with usb1_funct and usb_phy
>
> I am having a problem using bulkusb.sys ( XP DDK version running on a
> windows XP HOME SP1 PC). Occasionally (and randomly) I get 0xc000005
> returned when I try to send a packet to the device.
>
> I know that this means DEV_NOT_RESPONDING (from usbdi.h) but what does
> this actually mean. I do not have access to a protocol analyser and
> wondering whether this is a known issue with the driver or a problem with
> the device. I am using a fairchild transceiver with the usb1_funct and
> usb_phy which (apart from this) has operated perfectly.
>
> Could someone point me in the right direction
>
> 1) Has the device responded? If so, is it a corrupt response (i.e. a noise
> or timing issue). Has it stalled? According the device it has not stalled
> or had any CRC or overflow errors.
> 2) Can it be recovered (by some call into the driver, such as a reset)
> that will allow me to continue, or is it terminal. If I do nothing and
> simply try to write to using 'WriteFile' it just locks up.
>
> Thankyou, in advance, to anyone that bothers to reply to me!
>
> A reply from the www.usb.org <http://www.usb.org> forum has suggested that
> the means that the device has simply failed to respond. Why would this be?
> I currently have two bulk endpoints 1 IN and 1OUT. My OUT FIFO is empty.
>
>
> Matt
> << File: ATT12423654.txt >>
|
 |
Browse
