On Sat, 7 Sep 2013, joe M wrote: > Hello Alan, > > >> Just wanted to check if you have any suggestions on how to go about > >> debugging this issue. > > > > Nothing that I haven't mentioned previously. > > Thank you for your thoughts. I could not get a logic analyzer to > figure out the signals on the lines. But, I could log the usb > interrupts from the device though. In the end, you may need to figure out a way to analyze those signals. > Attached is the output when I have the old_scheme_first parameter set > to 1/Y. The device is recognized fine with a non-usb 3.0 port. > > When I log from the device, I see just the Port reset. I do not see > the Set-Address request (or, any other txn coming through) coming > through to the device. So either the host controller didn't actually send the Set-Address command, or else the device didn't recognize it. I can't think of any way to tell which occurred without analyzing the bus signals (unless perhaps you can locate a bug in the device). Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
