Hi Soeren,
thanks for taking the time to help me.
I tried different cables, among them the one that I use for a variety of
devices without any issues so far. I also attached it directly to the PC
rather than through the HUB I usually use.
xhci-hcd seems to be built in with newer kernels:
$ sudo modprobe -r xhci-hcd
modprobe: FATAL: Module xhci_hcd is builtin.
And it seem's it's not relevant here:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
I tried it on two different computers so far. But I will try it on more.
What else could I try?
Rgds
Richard
Am Freitag, den 19.06.2015, 17:22 +0200 schrieb Soeren Apel:
> Hi Richard,
>
> the cable shipped with such units has been found to cause issues
> more than once, so I'd recommend to try first with a different
> (i.e. higher-quality) one.
>
> If that doesn't help it might be worth the time to try and remove/
> blacklist the kernel module xhci-hcd as it has been the reason for
> LIBUSB_ERROR_TIMEOUT issues in *my* case.
>
> Not sure what your system-level knowledge is, so just in case:
> you can use "lsusb --tree" to check if the device is attached
> to a root hub that is serviced by xhci-hcd.
>
>
> All the best,
> -Soeren
>
>
>
> On Thu, 2015-06-18 at 23:51 +0200, Richard Ulrich wrote:
> > Hi,
> >
> > today I received my first ever logic analyzer, and subsequently found
> > and installed sigrok and pulseview from the ubuntu repository.
> > The software looks very good, but unfortunately, there is a problem
> > connecting to my device. It can find it, but connecting to it fails.
> >
> > This is the device :
> > http://www.sigrok.org/wiki/MCU123_USBee_AX_Pro_clone
> >
> > And this is the relevant part of the log:
> > sr: fx2lafw: Firmware upload was not needed.
> > sr: fx2lafw: Unable to get version info: LIBUSB_ERROR_TIMEOUT.
> > sr: fx2lafw: Failed to get firmware version.
> > sr: fx2lafw: Unable to open device.
> > Failed to configure sample count.
> > Failed to configure samplerate.
> > sr: session: Starting.
> > sr: session: sr_session_start: could not start an acquisition (device
> > closed but should be open)
> >
> > I couldn't find a troubleshooting section on the web page. So what are
> > the usual steps in cases like this?
> >
> > Rgds
> > Richard
> >
> >
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > sigrok-devel mailing list
> > sigrok-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/sigrok-devel
>
>
------------------------------------------------------------------------------
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
