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
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
>
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
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
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
5 matches
Mail list logo
