Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Paul Fertser]

On Tue, Mar 31, 2020 at 12:20:02PM +0300, Paul Fertser wrote:
> On Mon, Mar 30, 2020 at 02:39:47PM +0200, Martijn Scalé wrote:
> > sr: ezusb: uploading firmware to device on 2.22
> > sr: ezusb: setting CPU reset mode on...
> ...
> > sr: saleae-logic16: Waited 2976ms.
> > sr: saleae-logic16: Waited 3114ms.
> > sr: saleae-logic16: Device failed to renumerate.
> 
> You might want to reproduce this with LIBUSB_DEBUG=4 environment
> variable set. Worth a try with both WinUSB and libusb-win32, and
> please try to make your testing consistent, physically power-cycling
> the USB device is recommended.

Oh, and do not forget windows might be assigning different drivers
pre-firmware loading and post- (due to different VID/PID).

Another test would be to rerun libsigrok after the firmware was
loaded.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Paul Fertser]

On Mon, Mar 30, 2020 at 02:39:47PM +0200, Martijn Scalé wrote:
> sr: ezusb: uploading firmware to device on 2.22
> sr: ezusb: setting CPU reset mode on...
...
> sr: saleae-logic16: Waited 2976ms.
> sr: saleae-logic16: Waited 3114ms.
> sr: saleae-logic16: Device failed to renumerate.

You might want to reproduce this with LIBUSB_DEBUG=4 environment
variable set. Worth a try with both WinUSB and libusb-win32, and
please try to make your testing consistent, physically power-cycling
the USB device is recommended.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Martijn Scalé]

Hi,

Although I may be able to grab some data with WireShark, I am totally 
not familiar with USB implementations, so I am with you when you hope 
Sigrok developers would step in.


I may post some WireShark data later if I come round to it, for now, I 
will keep using libusb-win32 with the mcupro Logic16 clone.


Thanks for your time and replies.


On 30/03/2020 19:25, Paul Fertser wrote:

Hey,

On Mon, Mar 30, 2020 at 06:50:34PM +0200, Martijn Scalé wrote:

As for the libusb-win32 driver, I understood that it was deprecated, I read it

So nice you found a workaround. And something to compare with.


" We recently had an odd issue with OpenOCD on windows where a claim_interface
libusb API call was missing and it was giving weird errors as the result but
just on windows."

Could this still be related?

It might be related, yes. I'm not familiar with Sigrok codebase but
the idea is to check whether this driver runs claim_interface when
working on windows (and in fact it should be called on all systems,
just some are more forgiving).


Of course we are talking about a clone, and it does work with libusb-win32, but
with this driver being deprecated I am eager to get it working on WinUSB.
So your thoughts and input are highly appreciated!

At this point I hope sigrok developers can chime in. It might be a bug
in libusb too but I do not know how to gather enough debug info for
the libusb maintainers to fix it. First thing to try would be to make
sure claim_interface() is called. And then probably you can use
Wireshark to capture all USB traffic in both libusb-win32 and WinUSB
cases. That would make for a potentially useful bug report.





___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Paul Fertser]

Hey,

On Mon, Mar 30, 2020 at 06:50:34PM +0200, Martijn Scalé wrote:
> As for the libusb-win32 driver, I understood that it was deprecated, I read it

So nice you found a workaround. And something to compare with.

> " We recently had an odd issue with OpenOCD on windows where a claim_interface
> libusb API call was missing and it was giving weird errors as the result but
> just on windows."
> 
> Could this still be related?

It might be related, yes. I'm not familiar with Sigrok codebase but
the idea is to check whether this driver runs claim_interface when
working on windows (and in fact it should be called on all systems,
just some are more forgiving).

> Of course we are talking about a clone, and it does work with libusb-win32, 
> but
> with this driver being deprecated I am eager to get it working on WinUSB.
> So your thoughts and input are highly appreciated!

At this point I hope sigrok developers can chime in. It might be a bug
in libusb too but I do not know how to gather enough debug info for
the libusb maintainers to fix it. First thing to try would be to make
sure claim_interface() is called. And then probably you can use
Wireshark to capture all USB traffic in both libusb-win32 and WinUSB
cases. That would make for a potentially useful bug report.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Martijn Scalé]

Hi Paul,

Thanks for your answers! Let's start with the good news, I think you are 
right with regards to the second part, I have been fiddling around with 
short and long cables and may have moved to a new USB port on a HUB, 
when I stick to the same port each time it seems to "remember" it's driver.


As for the libusb-win32 driver, I understood that it was deprecated, I 
read it was in *Bug-Fix-Only maintenance mode* 
(https://sourceforge.net/p/libusb-win32/wiki/Home/).
However, I cannot seem to get the mcupro Logic16 clone working when 
selecting WinUSB. When using WinUSB, I get the following in my log:

sr: saleae-logic16: Found a Logic16 device.
sr: hwdriver: Scan found 1 devices (saleae-logic16).
sr: device: saleae-logic16: Opening device instance.
sr: saleae-logic16: Firmware upload was not needed.
saleae-logic16: Failed to receive reply to EP1 command 0x7d: 
LIBUSB_ERROR_IO.

sr: saleae-logic16: Failed to init device.
sr: saleae-logic16: Unable to open device.
Notifying user of session error: "generic/unspecified error"

which error message "Failed to receive reply to EP1 command 0x7d: 
LIBUSB_ERROR_IO" brings us back to the email that Dimitry Katsubo sent 
you earlier, with the same issue.


In your last email to Dimitry you mentioned:
" This might hint at something odd going on with the windows usb stack 
specifically. "

and
" We recently had an odd issue with OpenOCD on windows where a 
claim_interface libusb API call was missing and it was giving weird 
errors as the result but just on windows."


Could this still be related?
Of course we are talking about a clone, and it does work with 
libusb-win32, but with this driver being deprecated I am eager to get it 
working on WinUSB.

So your thoughts and input are highly appreciated!


On 30/03/2020 17:38, Paul Fertser wrote:

Hi Martijn!

On Mon, Mar 30, 2020 at 02:39:47PM +0200, Martijn Scalé wrote:

Opening the latest Zadig (2.5) (Options, List all Devices, select Logic S/16) I
change the drive to libusb-win32 (v1.2.6.0), succesfully.

Now this looks odd because libusb-win32 Windows kernel driver is used
by old libusb-0.1 API and long since deprecated. Windows software is
supposed to be using libusb-1 and that talks to microsoft "WinUSB"
driver.


The issue is that when you finish your work, close PulseView and disconnect the
analyser, when you start up again you have to again change the settings through
Zadig,

Now that's strange. AFAIK windows matches drivers not only by VID/PID
but also either by physical USB port used to attach or (depending on
IgnoreHWSerNum) by serial number in USB descriptor, see [0].

So if you loose the driver binding I think it means that something is
changing. Probably this device gets different serial number each boot?

[0] 
http://www.ftdichip.com/Support/Knowledgebase/index.html?ignorehardwareserialnumber.htm



___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Paul Fertser]

Hi Martijn!

On Mon, Mar 30, 2020 at 02:39:47PM +0200, Martijn Scalé wrote:
> Opening the latest Zadig (2.5) (Options, List all Devices, select Logic S/16) 
> I
> change the drive to libusb-win32 (v1.2.6.0), succesfully.

Now this looks odd because libusb-win32 Windows kernel driver is used
by old libusb-0.1 API and long since deprecated. Windows software is
supposed to be using libusb-1 and that talks to microsoft "WinUSB"
driver.

> The issue is that when you finish your work, close PulseView and disconnect 
> the
> analyser, when you start up again you have to again change the settings 
> through
> Zadig,

Now that's strange. AFAIK windows matches drivers not only by VID/PID
but also either by physical USB port used to attach or (depending on
IgnoreHWSerNum) by serial number in USB descriptor, see [0].

So if you loose the driver binding I think it means that something is
changing. Probably this device gets different serial number each boot?

[0] 
http://www.ftdichip.com/Support/Knowledgebase/index.html?ignorehardwareserialnumber.htm

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Martijn Scalé]

Hi Paul, Dimitri,

Hope you don't mind jumping on where you left the investigation.

I have access to both Windows 10 and Linux Ubuntu 18.04 and have the 
2018 variant of the mcupro Logic16 clone.
On Ubuntu, I have Sigrok-CLI 0.7.0, WIndows 10 uses PulseView 0.50 with 
libsigrok 0.6.0


As described in https://sigrok.org/wiki/Mcupro_Logic16_clone#Firmware:

"2015-01-08 and 2018 variants:  Only requires an upload of Cypress FX2LP 
firmware to operate. Open-source binaries from gregani 
 work, but must be renamed to 
*saleae-logic16-fx2.fw*."


I have used the three files from gregani and in Ubuntu was able to 
upgrade the firmware (put the three files in the newly created directory 
/usr/local/share/sigrok-firmware, fore reference, and had to run 
sigrok-cli as sudo). The lsusb -v information before and after the 
upgrade match the one shown on 
https://sigrok.org/wiki/Mcupro_Logic16_clone/Info.


On Windows,I have put the same three files in 
\Users\XYXYXY\AppData\Local\sigrok-firmware\ and using "pulseview -d 
saleae-logic16 -l 5":


sr: ezusb: uploading firmware to device on 2.22
sr: ezusb: setting CPU reset mode on...
sr: resource: Opened 
'C:\Users\XYXYXY\AppData\Local\sigrok-firmware\saleae-logic16-fx2.fw'.

sr: ezusb: Uploading firmware 'saleae-logic16-fx2.fw'.
sr: ezusb: Uploaded 4096 bytes.
sr: ezusb: Uploaded 1121 bytes.
sr: ezusb: Firmware upload done.
sr: ezusb: setting CPU reset mode off...
sr: hwdriver: Scan found 1 devices (saleae-logic16).
sr: device: saleae-logic16: Opening device instance.
sr: saleae-logic16: Waiting for device to reset.
sr: saleae-logic16: Waited 647ms.
sr: saleae-logic16: Waited 784ms.
sr: saleae-logic16: Waited 1016ms.
sr: saleae-logic16: Waited 1190ms.
sr: saleae-logic16: Waited 1386ms.
sr: saleae-logic16: Waited 1517ms.
sr: saleae-logic16: Waited 1648ms.
sr: saleae-logic16: Waited 1842ms.
sr: saleae-logic16: Waited 1974ms.
sr: saleae-logic16: Waited 2125ms.
sr: saleae-logic16: Waited 2326ms.
sr: saleae-logic16: Waited 2460ms.
sr: saleae-logic16: Waited 2613ms.
sr: saleae-logic16: Waited 2829ms.
sr: saleae-logic16: Waited 2976ms.
sr: saleae-logic16: Waited 3114ms.
sr: saleae-logic16: Device failed to renumerate.

Opening the latest Zadig (2.5) (Options, List all Devices, select Logic 
S/16) I change the drive to libusb-win32 (v1.2.6.0), succesfully.

Running Pulseview again ("pulseview -d saleae-logic16 -l 5"):

sr: saleae-logic16: Found a Logic16 device.
sr: hwdriver: Scan found 1 devices (saleae-logic16).
sr: device: saleae-logic16: Opening device instance.
sr: saleae-logic16: Firmware upload was not needed.
sr: saleae-logic16: mcupro Saleae16 detected.
sr: saleae-logic16: Opened device on 2.25 (logical) / usb/2-2.1.1 
(physical), interface 0.
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30014 (triggermatch) sdi 
03B0BE20 cg NULL -> [1, 2, 3, 4, 5]
sr: hwdriver: sr_config_list(): key 30023 (voltage_threshold) sdi 
03B0BE20 cg NULL -> [(0.69996, 1.3999), 
(1.3999, 3.6001)]
sr: hwdriver: sr_config_get(): key 30023 (voltage_threshold) sdi 
03B0BE20 cg NULL -> (0.69996, 1.3999)
sr: hwdriver: sr_config_get(): key 30023 (voltage_threshold) sdi 
03B0BE20 cg NULL -> (0.69996, 1.3999)
sr: hwdriver: sr_config_get(): key 30001 (captureratio) sdi 
03B0BE20 cg 

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Paul Fertser]

Hi,

On Tue, Jan 14, 2020 at 12:30:17AM +0100, Dmitry Katsubo via sigrok-devel wrote:
> I have extracted the firmware from Logic v1.2.10 and placed it to
> the necessary directory. Now PulseView fails with the following log:
> sr: resource: Opened 
> '...\PulseView\share\sigrok-firmware\saleae-logic16-fx2.fw'.
...
> saleae-logic16: Failed to receive reply to EP1 command 0x7d: LIBUSB_ERROR_IO.
> sr: saleae-logic16: Failed to init device.

Were you able to solve this issue? This might hint at something odd
going on with the windows usb stack specifically. Is there a chance
you can try the same version with the same hardware using GNU/Linux?
Then you'll have more debug data from the kernel, "lsusb -v" etc.

We recently had an odd issue with OpenOCD on windows where a
claim_interface libusb API call was missing and it was giving weird
errors as the result but just on windows.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Dmitry Katsubo via sigrok-devel]

Hello,

I have extracted the firmware from Logic v1.2.10 and placed it to the necessary 
directory. Now PulseView fails with the following log:

sr: resource: Opened 
'...\PulseView\share\sigrok-firmware\saleae-logic16-fx2.fw'.
sr: ezusb: Uploading firmware 'saleae-logic16-fx2.fw'.
sr: ezusb: Uploaded 4096 bytes.
sr: ezusb: Uploaded 1121 bytes.
sr: ezusb: Firmware upload done.
sr: ezusb: setting CPU reset mode off...
sr: hwdriver: Scan found 1 devices (saleae-logic16).
sr: device: saleae-logic16: Opening device instance.
sr: saleae-logic16: Waiting for device to reset.
sr: saleae-logic16: Waited 594ms.
...
sr: saleae-logic16: Waited 2021ms.
saleae-logic16: Failed to receive reply to EP1 command 0x7d: LIBUSB_ERROR_IO.
sr: saleae-logic16: Failed to init device.
sr: saleae-logic16: Waited 2132ms.
...
sr: saleae-logic16: Device failed to renumerate.
Notifying user of session error: "generic/unspecified error"

I think, what can be improved is that the error message "Failed to receive 
reply to EP1 command 0x7d: LIBUSB_ERROR_IO" is shown to the user, that's anyway 
better than "generic/unspecified error".

On 2020-01-12 13:39, Dmitry Katsubo wrote:
> Hello,
> 
> On 2020-01-10 11:07, Paul Fertser wrote:
>> Saleae is using its own firmware and also probably the kernel driver
>> they install is not providing WinUSB API.
>>
>> Since you're on windows, have you tried using Zadig to install WinUSB
>> driver for this device?
> 
> I have uninstalled Saleae software and drivers (just to have everything 
> clean) and then I have installed WinUSB (v6.1.7600.16385) via Zadig (see 
> attached screenshot). I run PulseView and got the same
> error (see below for transcript).
> 
> On 2020-01-10 10:50, soe...@apelpie.net wrote:
>> Yes, you can do that. Either run "pulseview -l 5" from the command line or
>> open the settings dialog, go to logging, set the log level to 5 and try to
>> connect to the Saleae Logic 16.
>>
>> Then you can go back to the logging window and have a look at what it says 
>> there.
> 
> Thanks for pointing that out. It turned out that PulseView was trying to 
> locate a different firmware:
> 
> sr: backend: libsigrok 0.5.1/5:0:1 (rt: 0.5.1/5:0:1).
> sr: backend: Libs: glib 2.44.1 (rt: 2.44.1/4401:1), libzip 1.5.1, 
> libserialport 0.1.1/1:0:1 (rt: 0.1.1/1:0:1), libusb-1.0 1.0.20.11003-rc3 API 
> 0x01000104, libftdi 1.2.
> sr: backend: Host: x86_64-w64-mingw32.static.posix, little-endian.
> ...
> sr: hwdriver: Scan found 0 devices (saleae-logic-pro).
> sr: ezusb: uploading firmware to device on 3.15
> sr: ezusb: setting CPU reset mode on...
> sr: resource: Attempt to open 
> '...\PulseView\share\sigrok-firmware\saleae-logic16-fx2.fw' failed: No such 
> file or directory
> sr: saleae-logic16: Firmware upload failed, name saleae-logic16-fx2.fw.
> sr: hwdriver: Scan found 1 devices (saleae-logic16).
> sr: device: saleae-logic16: Opening device instance.
> sr: saleae-logic16: Firmware upload was not needed.
> saleae-logic16: Failed to open device: LIBUSB_ERROR_ACCESS.
> sr: saleae-logic16: Unable to open device.
> Notifying user of session error: "generic/unspecified error"
> 
> while correct (or, let's say, one that is present) is 
> '...\PulseView\share\sigrok-firmware\fx2lafw-saleae-logic.fw'
> 
> I got confused... Where to get saleae-logic16-fx2.fw from? It is not a part 
> of binary download [1], right?
> 
> While trying to locate it I found the issue #650 which looks to be the same 
> as I experience. In particular comment#3 reads:
> 
>> You should use the "sigrok-fwextract-saleae-logic16" [3] script mentioned in 
>> the wiki to extract the three firmware/bitstream files from the Saleae 
>> software.
>> 1. Download the Linux version (either 32-bit or 64-bit will do), and unpack 
>> it to find the main binary called "Logic".
>> 2. To extract the firmware/bitstreams, run the following command:
>> $ sigrok-fwextract-saleae-logic16 Logic"
> 
> On the other hand comments #22
> 
>> $ pulseview -l 3
>> sr: saleae-logic16: Firmware upload was not needed.
>> sr: saleae-logic16: mcupro Saleae16 detected.
>> sr: saleae-logic16: Opened device on 20.11 (logical) / usb/20-2 (physical),
> 
> and #25
> 
>> Finally got it working on all my Windows 7/10 Systems.
>> This is what i did, with Zadiag:
>> Install libusb-Driver, re-connect Device, install winUSB-Driver, re-connect 
>> Device, install libusbK, re-connect Device, then again installed libusb.
>> And voila, started Pulsview and all OK.
> 
> generally assume that no firmware is needed. WinUSB driver was installed by 
> PulseView, right? So I decided to install libusb driver as that comment 
> advises. However instructions on [4] generally
> contradict with comment #25:
> 
>> Currently, this means installing *one of* Microsoft's WinUSB, libusb-win32 
>> or libusbK drivers.
>> Use the most recent version of Zadig, an Automated Driver Installer GUI 
>> application for WinUSB (recommended), libusb-win32 (not working well, not 
>> recommended) and libusbK (only if you 

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Dmitry Katsubo via sigrok-devel]

Hello,

On 2020-01-10 11:07, Paul Fertser wrote:
> Saleae is using its own firmware and also probably the kernel driver
> they install is not providing WinUSB API.
> 
> Since you're on windows, have you tried using Zadig to install WinUSB
> driver for this device?

I have uninstalled Saleae software and drivers (just to have everything clean) 
and then I have installed WinUSB (v6.1.7600.16385) via Zadig (see attached 
screenshot). I run PulseView and got the same
error (see below for transcript).

On 2020-01-10 10:50, soe...@apelpie.net wrote:
> Yes, you can do that. Either run "pulseview -l 5" from the command line or
> open the settings dialog, go to logging, set the log level to 5 and try to
> connect to the Saleae Logic 16.
>
> Then you can go back to the logging window and have a look at what it says 
> there.

Thanks for pointing that out. It turned out that PulseView was trying to locate 
a different firmware:

sr: backend: libsigrok 0.5.1/5:0:1 (rt: 0.5.1/5:0:1).
sr: backend: Libs: glib 2.44.1 (rt: 2.44.1/4401:1), libzip 1.5.1, libserialport 
0.1.1/1:0:1 (rt: 0.1.1/1:0:1), libusb-1.0 1.0.20.11003-rc3 API 0x01000104, 
libftdi 1.2.
sr: backend: Host: x86_64-w64-mingw32.static.posix, little-endian.
...
sr: hwdriver: Scan found 0 devices (saleae-logic-pro).
sr: ezusb: uploading firmware to device on 3.15
sr: ezusb: setting CPU reset mode on...
sr: resource: Attempt to open 
'...\PulseView\share\sigrok-firmware\saleae-logic16-fx2.fw' failed: No such 
file or directory
sr: saleae-logic16: Firmware upload failed, name saleae-logic16-fx2.fw.
sr: hwdriver: Scan found 1 devices (saleae-logic16).
sr: device: saleae-logic16: Opening device instance.
sr: saleae-logic16: Firmware upload was not needed.
saleae-logic16: Failed to open device: LIBUSB_ERROR_ACCESS.
sr: saleae-logic16: Unable to open device.
Notifying user of session error: "generic/unspecified error"

while correct (or, let's say, one that is present) is 
'...\PulseView\share\sigrok-firmware\fx2lafw-saleae-logic.fw'

I got confused... Where to get saleae-logic16-fx2.fw from? It is not a part of 
binary download [1], right?

While trying to locate it I found the issue #650 which looks to be the same as 
I experience. In particular comment#3 reads:

> You should use the "sigrok-fwextract-saleae-logic16" [3] script mentioned in 
> the wiki to extract the three firmware/bitstream files from the Saleae 
> software.
> 1. Download the Linux version (either 32-bit or 64-bit will do), and unpack 
> it to find the main binary called "Logic".
> 2. To extract the firmware/bitstreams, run the following command:
> $ sigrok-fwextract-saleae-logic16 Logic"

On the other hand comments #22

> $ pulseview -l 3
> sr: saleae-logic16: Firmware upload was not needed.
> sr: saleae-logic16: mcupro Saleae16 detected.
> sr: saleae-logic16: Opened device on 20.11 (logical) / usb/20-2 (physical),

and #25

> Finally got it working on all my Windows 7/10 Systems.
> This is what i did, with Zadiag:
> Install libusb-Driver, re-connect Device, install winUSB-Driver, re-connect 
> Device, install libusbK, re-connect Device, then again installed libusb.
> And voila, started Pulsview and all OK.

generally assume that no firmware is needed. WinUSB driver was installed by 
PulseView, right? So I decided to install libusb driver as that comment 
advises. However instructions on [4] generally
contradict with comment #25:

> Currently, this means installing *one of* Microsoft's WinUSB, libusb-win32 or 
> libusbK drivers.
> Use the most recent version of Zadig, an Automated Driver Installer GUI 
> application for WinUSB (recommended), libusb-win32 (not working well, not 
> recommended) and libusbK (only if you hit WinUSB
limitations).

Now I am lost what to do next...

Thanks in advance for help.

[1] https://sigrok.org/download/binary/sigrok-firmware-fx2lafw/
[2] https://sigrok.org/bugzilla/show_bug.cgi?id=650#c3
[3] 
https://sigrok.org/gitweb/?p=sigrok-util.git;a=tree;f=firmware/saleae-logic16
[4] https://github.com/libusb/libusb/wiki/Windows#driver-installation

-- 
With best regards,
Dmitry
___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Paul Fertser]

Hello,

On Fri, Jan 10, 2020 at 09:54:43AM +0100, Dmitry Katsubo via sigrok-devel wrote:
> P.S. I have checked that device works properly (I was able to make a
> capture) with Saleae software. By looking at LED blinking I also see
> that it uploads its firmware successfully at startup. I tried also
> to launch PulseView after exiting Saleae (so that device is still
> initialized with a firmware) but it didn't help.

Saleae is using its own firmware and also probably the kernel driver
they install is not providing WinUSB API.

Since you're on windows, have you tried using Zadig to install WinUSB
driver for this device?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[soeren]

Hello Dmitry,


No worries. Maybe PulseView can be run in verbose mode so that it
generates more detailed log? Or maybe message could be further
improved / extended to bring more light on the issue? (e.g. "Firmware
was not found", "Failed to upload firmware", etc).


Yes, you can do that. Either run "pulseview -l 5" from the command line 
or
open the settings dialog, go to logging, set the log level to 5 and try 
to

connect to the Saleae Logic 16.

Then you can go back to the logging window and have a look at what it 
says there.


All the best,
 -Soeren


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Federico Cerutti]

Hi,
According to the wiki
https://sigrok.org/wiki/Firmware#Windows
you should put the firmware in the following path
C:\Program Files (x86)\sigrok\PulseView\share\sigrok-firmware
and pulseview will deal with uploading it to the device at the right
time. At the same time the wiki also says that the file should be
already there, as it it a redistributable package.
Check first if it already in place, then I honestly don't know what
could be wrong. The only other time I had that error message was when
I was missing the firmware, but being on Arch linux I simply grabbed
the right aur package and pacman dealt with the issue for me :-)

I can't help you about the Logic issue either, since I've never used
the two tools in conjunction, only one OR the other.
You could have a look at pulseview/libsigrok code to check how it
expects the csv data to be.

Sorry for the mostly unhelpful reply,
Federico

On 2020-01-06 01:33, Dmitry Katsubo via sigrok-devel wrote:

Thanks for reply!

I tried to jump into the subject but it seems that there are too many
unfamiliar things for me, excuses for dummy questions.

First I tried to understand how fx2lafw works. The wiki page says it
is a firmware, but where to get the loader for Windows? Looking at
wiki page you've mentioned I suppose that for Debian the
standard mechanism is used to load the firmware via udev trigger, but
what to do on Windows?

Then I thought I can use suggested software Logic 1.2.29 [1] to
capture the data and then I can export it and open in PulseView for
further analysis. First I discovered that Logic saves into
.logicdata file which cannot be opened by PulseView. The I tried to
export the data into CSV (see attached screenshot) with default
settings, but when I open it with PulseView it just hangs... :(

Another question is: Once the device is uploaded the fx2lafw firmware,
will it be still usable by Logic, i.e. will Logic re-upload firmware
on each application start?

Thanks!

[1] https://downloads.saleae.com/logic/1.2.29/Logic+Setup+1.2.29.exe

On 2020-01-05 16:45, Federico Cerutti wrote:

Hello,
You need the firmware for the Cypress IC inside your device.
Take a look at this wiki page:
https://sigrok.org/wiki/Mcupro_Logic16_clone
In the above page there is a link to pre built binaries

Additional information on the firmware itself:
https://sigrok.org/wiki/Fx2lafw

Best Regards


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel


--
Federico Cerutti


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Dmitry Katsubo via sigrok-devel]

Thanks for reply!

I tried to jump into the subject but it seems that there are too many 
unfamiliar things for me, excuses for dummy questions.

First I tried to understand how fx2lafw works. The wiki page says it is a 
firmware, but where to get the loader for Windows? Looking at wiki page you've 
mentioned I suppose that for Debian the
standard mechanism is used to load the firmware via udev trigger, but what to 
do on Windows?

Then I thought I can use suggested software Logic 1.2.29 [1] to capture the 
data and then I can export it and open in PulseView for further analysis. First 
I discovered that Logic saves into
.logicdata file which cannot be opened by PulseView. The I tried to export the 
data into CSV (see attached screenshot) with default settings, but when I open 
it with PulseView it just hangs... :(

Another question is: Once the device is uploaded the fx2lafw firmware, will it 
be still usable by Logic, i.e. will Logic re-upload firmware on each 
application start?

Thanks!

[1] https://downloads.saleae.com/logic/1.2.29/Logic+Setup+1.2.29.exe

On 2020-01-05 16:45, Federico Cerutti wrote:
> Hello,
> You need the firmware for the Cypress IC inside your device.
> Take a look at this wiki page:
> https://sigrok.org/wiki/Mcupro_Logic16_clone
> In the above page there is a link to pre built binaries
> 
> Additional information on the firmware itself:
> https://sigrok.org/wiki/Fx2lafw
> 
> Best Regards

-- 
With best regards,
Dmitry
Time[s], Channel 0
0.000, 1
0.99894325000, 0
0.99895175000, 1
0.99896025000, 0
0.99896875000, 1
0.99897725000, 0
0.99900275000, 1
0.99901125000, 0
0.99901975000, 1
0.99902825000, 0
0.99904525000, 1
0.99905375000, 0
0.99907075000, 1
0.99909625000, 0
0.99910475000, 1
0.99911325000, 0
0.99913025000, 1
0.99913875000, 0
0.99915575000, 1
0.99918125000, 0
0.99918975000, 1
0.99919825000, 0
0.99920668750, 1
0.99924068750, 0
0.99924918750, 1
0.99926618750, 0
0.99927468750, 1
0.99928318750, 0
0.99930018750, 1
0.99930868750, 0
0.99932568750, 1
0.99935118750, 0
0.99935968750, 1
0.99936818750, 0
0.99941918750, 1
0.99942768750, 0
0.99944468750, 1
0.99945318750, 0
0.99946168750, 1
0.99947868750, 0
0.99950412500, 1
0.99952112500, 0
0.99952962500, 1
0.99953812500, 0
0.99954662500, 1
0.99958062500, 0
0.99958912500, 1
0.99960612500, 0
0.99961462500, 1
0.99962312500, 0
0.99964862500, 1
0.99965712500, 0
0.99967412500, 1
0.99969112500, 0
0.99969962500, 1
0.99970812500, 0
0.99971662500, 1
0.99972512500, 0
0.99973362500, 1
0.99974212500, 0
0.99975912500, 1
0.99977612500, 0
0.99978462500, 1
0.99979312500, 0
0.99984406250, 1
0.99985256250, 0
0.99986956250, 1
0.99987806250, 0
0.99988656250, 1
0.99989506250, 0
0.2056250, 1
0.3756250, 0
0.5456250, 1
0.6306250, 0
0.7156250, 1
0.8006250, 0
0.8856250, 1
1.0556250, 0
1.3956250, 1
1.4806250, 0
1.6506250, 1
1.7356250, 0
1.8206250, 1
1.9056250, 0
1.0001245, 1
4.08454337500, 0
4.08455181250, 1
4.08456881250, 0
4.08458581249, 1
4.08459431250, 0
4.08460281250, 1
4.08461131250, 0
4.08461981250, 1
4.08462831250, 0
4.08463681249, 1
4.08464531250, 0
4.08465381250, 1
4.08466231250, 0
4.08467931250, 1
4.08469631250, 0
4.08470481250, 1
4.08471331250, 0
4.08473881249, 1
4.08474731250, 0
4.08475581250, 1
4.08478131250, 0
4.08478981250, 1
4.08479831250, 0
4.08482381250, 1
4.08483231250, 0
4.08484081250, 1
4.08486625000, 0
4.08487475000, 1
4.08488325000, 0
4.08489175000, 1
4.08490025000, 0
4.08491725000, 1
4.08492575000, 0
4.08493425000, 1
4.08495125000, 0
4.08495974999, 1
4.08496825000, 0
4.08498525000, 1
4.08501074999, 0
4.08501925000, 1
4.08503625000, 0
4.08504475000, 1
4.08505325000, 0
4.08506174999, 1
4.08508725000, 0
4.08510425000, 1
4.08512125000, 0
4.08512975000, 1
4.08513825000, 0
4.08518918750, 1
4.08519768750, 0
4.08521468750, 1
4.08522318750, 0
4.08523168749, 1
4.08524018750, 0
4.08524868750, 1
4.08525718750, 0
4.08526568750, 1
4.08529118750, 0
4.08529968750, 1
4.08530818750, 0
4.08535068750, 1
4.08537618750, 0
4.08538468750, 1
4.08539318750, 0
4.08544418749, 1
4.08545268750, 0
4.08546968750, 1
4.08547818750, 0
4.08548668750, 1
4.08549518749, 0
4.08550362499, 1
4.08551212500, 0
4.08552912500, 1
4.08554612500, 0
4.08555462499, 1
4.08556312500, 0
4.08558862500, 1
4.08559712500, 0
4.08560562499, 1
4.08563112500, 0
4.08563962500, 1

Re: [sigrok-devel] Using Saleae Logic 16 clone with PulseView

[Federico Cerutti]

Hello,
You need the firmware for the Cypress IC inside your device.
Take a look at this wiki page:
https://sigrok.org/wiki/Mcupro_Logic16_clone
In the above page there is a link to pre built binaries

Additional information on the firmware itself:
https://sigrok.org/wiki/Fx2lafw

Best Regards

On 2020-01-05 16:08, Dmitry Katsubo via sigrok-devel wrote:

Dear Sigrok develoeprs,

I would like to use latest PulseView v0.4.1 with this Saleae Logic 16
clone [1] (looks exactly the same as "black" mod on page Noname
XL-LOGIC16-100M [2]).

I have downloaded drivers from Saleae website [3] and installed them.
After that when I select "Saleae Logic 16" from driver list and press
"Scan for devices", PulseViewis is able to detect Saleae Logic16:

Unfortunately when I press OK, it shows the error "Failed to open
device. generic/unspecified error":

Is there any chance to make it working?

Thanks in advance!

--
With best regards,
Dmitry


Links:
--
[1] https://www.aliexpress.com/item/32613420798.html?
[2] https://sigrok.org/wiki/Noname_XL-LOGIC16-100M
[3] 
https://downloads.saleae.com/logic/1.2.29/Logic+1.2.29+Win+64+Standalone.zip

___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel


--
Federico Cerutti


___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel