|
Message
From: gayathri seshadri<gaysesh@h...>
Date: Fri Oct 15 12:09:28 CEST 2004
Subject: [usb] bulkusb.sys with usb1_funct and usb_phy
Hi,What is the backend interface of the usb device ?
i.e., Who takes care of emptying the data that you are trying to write to
the device's OUT endpoint( from the host)?
Normally, NAK is a response given when there is no room in the OUT endpoint
buffer for further data. Hence, my suggestion is to check if the logic
responsible for emptying the endpoint is rightly doing the job!!!!
May be it is a master on some bus and had not got its grant for a long
time.. from the arbiter of that bus.. etc..,
Just let me know if this helps..
Let me know even otherwise, what is the progress on this..
:-)
Thanks,
Gayathri Seshadri.
>From: "Matt Gillespie" <matt.gillespie@j...>
>Reply-To: "Discussion list about free,open source USB IP core"
><usb@o...>
>To: "Discussion list about free,open source USB IP core"
><usb@o...>
>Subject: RE: [usb] bulkusb.sys with usb1_funct and usb_phy
>Date: Thu, 14 Oct 2004 08:22:27 +0100
>
>Here are the results with the Hitex USB protocol analyser which seems to be
>really good bit of kit.
>
> recorded7.usb
>Page 1
> Hidden Line(s): SOF
> Hidden Columns(s):
> PID IDLE P# SYNCH PID FUNC DATA
>CRC5/16 time
>
>____________________________________________________________________________
>_____________________________
> > OUT 7551 00000001 0xE1 ADDR/EP
>0x01/0x01 0x1A 188.953 .
> > DAT. 7552 00000001 0xC3 DATA
>(64)
>01 80 B7 02 00 00 00. 0x1B71 45.50 us
> < ACK 7553 00000001 0xD2
>1.50 us
> > OUT 7784 00000001 0xE1 ADDR/EP
>0x01/0x01 0x1A 229.953 .
> > DAT. 7785 00000001 0x4B DATA
>(64)
>01 80 F4 00 00 00 00. 0x5E64 45.50 us
> < ACK 7786 00000001 0xD2
>1.50 us
> > OUT 7998 00000001 0xE1 ADDR/EP
>0x01/0x01 0x1A 210.953 .
> > DAT. 7999 00000001 0xC3 DATA
>(64)
>01 81 31 00 A8 FB 00. 0xE89B 45.50 us
> < ACK 8000 00000001 0xD2
>1.50 us
> > OUT 8269 00000001 0xE1 ADDR/EP
>0x01/0x01 0x1A 267.953 .
> > DAT. 8270 00000001 0x4B DATA
>(64)
>01 81 6E 00 00 00 00. 0xFE4A 45.50 us
> > OUT 8271 00000001 0xE1 ADDR/EP
>0x01/0x01 0x1A 2.83 us
> > DAT. 8272 00000001 0x4B DATA
>(64)
>01 81 6E 00 00 00 00. 0xFE4A 45.50 us
> < NAK 8273 00000001 0x5A
>1.50 us
> > OUT 8274 00000001 0xE1 ADDR/EP
>0x01/0x01 0x1A 2.83 us
>
> > DAT. 8275 00000001 0x4B DATA
>(64)
>01 81 6E 00 00 00 00. 0xFE4A 45.50 us
> < NAK 8276 00000001 0x5A
>1.50 us
> > OUT 8277 00000001 0xE1 ADDR/EP
>0x01/0x01 0x1A 2.83 us
> > DAT. 8278 00000001 0x4B DATA
>(64)
>01 81 6E 00 00 00 00. 0xFE4A 45.50 us
> < NAK 8279 00000001 0x5A
>1.50 us
> > OUT 8280 00000001 0xE1 ADDR/EP
>0x01/0x01 0x1A 2.83 us
> > DAT. 8281 00000001 0x4B DATA
>(64)
>01 81 6E 00 00 00 00. 0xFE4A 45.50 us
> < NAK 8282 00000001 0x5A
>
>The problem appears to start at 8269. A DAT following by ACK does not have
>a
>reply. From now on every transaction is NACK'ed. I have tested ep_full and
>it remains low during the NAK period. I guess that this transaction was
>aborted but the SIE does not appear to recover. All these transactions are
>taking place at Full speed. My oscillator is a 48MHz Osc module so I dont
>think that there are any baud rate problems.
>
>Anyone seen anything like this before.
>
>
>Thanks
>
>Matt
>
>
>
>
> -----Original Message-----
>From: usb-bounces@o... [mailto:usb-bounces@o...] On
>Behalf Of Trainee IAC, (IE10)
>Sent: 11 October 2004 10:11
>To: 'Discussion list about free,open source USB IP core'
>Subject: RE: [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 >>
>_______________________________________________
>http://www.opencores.org/mailman/listinfo/usb
>
>_______________________________________________
>http://www.opencores.org/mailman/listinfo/usb
_________________________________________________________________
All the news that matters. All the gossip from home.
http://www.msn.co.in/NRI/ Specially for NRIs!
|
 |
Browse
