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

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

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

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

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

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

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

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 > l

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

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 dri

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

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

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

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 describ

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

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-logi

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

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: Uploa

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

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 softwar

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

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

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

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 r

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

Hello, On 2020-01-06 23:10, Federico Cerutti wrote: > 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

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

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

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

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

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

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

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

Dear Sigrok develoeprs, I would like to use latest PulseView v0.4.1 with this Saleae Logic 16 clone (looks exactly the same as "black" mod on page Noname XL-LOGIC16-100M ). I have downloaded driv