OK. So I found what the problem is. Apparently during the build of Pulseview on
MacOS 10.12.5 the directory
"/usr/local/Cellar/libsigrok/HEAD-64f628b/share/sigrok-firmware” is not created
so there is no “fx2lafw” available for my USBee AX clone. Once I created the
directory and put the correct fw file(copied over from the Linux virtual
machine) in it, all is well.
I did finally determine that "sigrok-cli -l 5 —scan” would reveal where the
problem was.
The reason that run Pulseview in Linux would make the Mac side work was that
the Linux side of the machine renames the device on the USB bus from
“Vendor-Specific Device” to “fx2lafw”. This means that when Pulseview does the
scan it finds the name “fx2lafw” and carries on. Now the same thing happens
with the Mac side.
Is there a reason why the "sigrok-firmware” directory is not created during the
build of Pulseview on MacOS 10.12.5?
Thanks,
Paul Crawford
> On May 18, 2017, at 13:19, paulcrawfordgm <paulcrawfor...@gmail.com> wrote:
>
> Hi,
>
> Yesterday, with a lot of help from James Burgess, I was finally able to build
> Pulseview for MacOS 10.12.5.
>
> Today, I tried to use it to monitor a UART on an Atmel Mega328p. It did
> finally work successfully but there were again many roadblocks on the way.
>
> When I tried to connect to my device, a USBee AX clone, I got the following
> error output on Terminal:
>
> sr: resource: Failed to open resource 'fx2lafw-cwav-usbeeax.fw
> <http://fx2lafw-cwav-usbeeax.fw/>' (use loglevel 5/spew for details).
> sr: fx2lafw: Firmware upload failed for device 20.18 (logical).
> sr: fx2lafw: Unable to get version info: LIBUSB_ERROR_TIMEOUT.
> sr: fx2lafw: Failed to get firmware version.
> sr: fx2lafw: Unable to open device.
>
> I had previously built Pulseview on a Parallels Ubuntu 16.04 virtual machine
> on the Mac. I found that the only way to connect to the USBee AX was to get
> Pulseview running on the Linux virtual machine, then exit Pulseview there,
> release the USB connection from Linux to the Mac and then connect to the
> device on the Mac side. While this works reliably, it is clearly not the
> preferred solution.
>
> Can anyone determine from the above errors what is causing the problem? When
> I connect the device to the Mac I can see it System Information Hardware USB
> but it will not get connected to Pulseview. When it is connected to
> Pulseview, using the above technique, it shows up in System Information as
> “fx2lafw” rather than “Vendor Specific” when it is first connected.
>
> Thanks for any help.
>
> Paul Crawford
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
