ok,
this is a plausible explanation for the observed bahviour.
i have to admit that i was not thinking of non-gcc compilers when i used
"__attribute__((packed))" in that code-base. does you compiler silently
ignore them or is there a warning?
as it is non-standard i tend to rewrite affected
ubject: Re: [sigrok-devel] Getting firmware for Kingston LA2016
(just my guess on reported run_state's)
my assumption is that run_state 0x85e_2_ is meaning "waiting for trigger
condition".
from your other log output i see that there is no edge/level-trigger
requested, device should just
(just my guess on reported run_state's)
my assumption is that run_state 0x85e_2_ is meaning "waiting for trigger
condition".
from your other log output i see that there is no edge/level-trigger
requested, device should just start sampling 200M samples no matter what
signals are applied...
and
hi helge,
TL;DR: can someone help helge with creating a usb trace on windows?
attached is a log file from running the command
sigrok-cli -l 5 -d kingst-la2016 --samples 200M -O binary -o test.bin
on my linux machine (debian kernel 4.19.0-2-amd64 with debian's
libusb-1.0-0 version 1.0.22 on
...@gmail.com]
Sent: Tuesday, October 27, 2020 5:39 PM
To: Helge Kruse
Cc: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] Getting firmware for Kingston LA2016
Hey!
On Tue, Oct 27, 2020 at 02:30:42PM +0100, Helge Kruse wrote:
> I am not sure what configuration should be set here. I wo
Hey!
On Tue, Oct 27, 2020 at 02:30:42PM +0100, Helge Kruse wrote:
> I am not sure what configuration should be set here. I would be interesting
> to see a successful operation with that device on a Linux PC hardware. Could
> you generate a similar log with "sigrok-cli --scan" and send it to me?
chip you have.
Well, at least the log tells me that the firmware upload was successful.
Best regards,
Helge
-Original Message-
From: Paul Fertser [mailto:fercer...@gmail.com]
Sent: Sunday, October 18, 2020 12:08 PM
To: Helge Kruse
Cc: sigrok-devel@lists.sourceforge.net
Subject: Re: [si
On Sun, Oct 18, 2020 at 11:46:43AM +0200, Helge Kruse wrote:
> Anyway, the nightly build should support the LA2016. The --scan result is
> attached. The essential lines are probably:
> sr: [00:01.403000] kingst-la2016: Found a LA2016 device.
> sr: [00:01.403000] kingst-la2016: device at 'usb/2-8'
Ouch, I missed to attach the log.
-Original Message-
From: Helge Kruse [mailto:helge.kr...@gmx.net]
Sent: Sunday, October 18, 2020 11:47 AM
To: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] Getting firmware for Kingston LA2016
Hi Paul,
> I think you're supposed to
cer...@gmail.com]
Sent: Sunday, October 18, 2020 10:47 AM
To: Helge Kruse
Cc: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] Getting firmware for Kingston LA2016
On Sun, Oct 18, 2020 at 10:32:31AM +0200, Helge Kruse wrote:
> I started "sigrok-cli -L -l5 > sigrok-cli.log 2&
On Sun, Oct 18, 2020 at 10:32:31AM +0200, Helge Kruse wrote:
> I started "sigrok-cli -L -l5 > sigrok-cli.log 2>&1". The output is attached,
I think you're supposed to run --scan for any detection attempts to
take place.
Also, the support was added with
rceforge.net
Subject: Re: [sigrok-devel] Getting firmware for Kingston LA2016
On Sun, Oct 18, 2020 at 10:17:46AM +0200, Helge Kruse wrote:
> Thanks for the input. I have installed WinUSB (v6.1.7600.16385) for the
> device "Unknown Device #1" using Zadig. This didn't change th
On Sun, Oct 18, 2020 at 10:17:46AM +0200, Helge Kruse wrote:
> Thanks for the input. I have installed WinUSB (v6.1.7600.16385) for the
> device "Unknown Device #1" using Zadig. This didn't change the list
> "Supported hardware drivers" in the output of "sigrok-cli -L".
I suggest you enable more
ilto:fercer...@gmail.com]
Sent: Sunday, October 18, 2020 10:05 AM
To: Helge Kruse
Cc: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] Getting firmware for Kingston LA2016
Hello,
On Sun, Oct 18, 2020 at 09:26:56AM +0200, Helge Kruse wrote:
> I assume that it's not necessary to insta
Hello,
On Sun, Oct 18, 2020 at 09:26:56AM +0200, Helge Kruse wrote:
> I assume that it's not necessary to install the libusb driver with
> Zadig. Am I right?
For the reference, Zadig allows installing one of the three drivers:
1. WinUSB; 2. libusb-win32; 3. libusbK. As confusing as it might
regards,
Helge
-Original Message-
From: Florian Schmidt [mailto:schmidt_flor...@gmx.de]
Sent: Saturday, October 17, 2020 7:46 PM
To: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] Getting firmware for Kingston LA2016
to me it looks like you only downloaded this single
&
to me it looks like you only downloaded this single
"sigrok-fwextract-kingst-la2016" script, instead of doing a git-clone of
the sigrok-util repo or unpacking a snapshot-zip file. this script is
not stand-alone, it needs this parseelf.py file from another folder in
that same repository.
can you
Hi,
I got a LA2016 from Kingston and want to use it with sigrok (PulseView 0.5.0
and sigrok-cli 0.7.1). The wiki (https://sigrok.org/wiki/Kingst_LA2016)
describes some manual steps to get the firmware:
- Download sigrok-fwextract-kingst-la2016 and place them in one of
the usual places
18 matches
Mail list logo
