[sigrok-devel] [PATCH 4/4] Refactor and bugfix the delay adding code for analog capture
There're two essential modifications in this change:
1. Fix timing for capture frequencies less than 200 kHz;
2. Sample ADC output after CLK is set low, as per the TLC5510
datasheet.
The second point is also important as the capture state sets CLK low,
so with the previous code there might have been a very short glitch on
this line during capture. Not confirmed by measurements, but it's
cleaner this way.
Signed-off-by: Paul Fertser <fercer...@gmail.com>
---
gpif-acquisition.c | 34 ++
1 file changed, 18 insertions(+), 16 deletions(-)
diff --git a/gpif-acquisition.c b/gpif-acquisition.c
index 09a56ca..dbf7403 100644
--- a/gpif-acquisition.c
+++ b/gpif-acquisition.c
@@ -212,27 +212,29 @@ bool gpif_acquisition_start(const struct
cmd_start_acquisition *cmd)
bmGSTATE | bmIFGPIF;
}
+ /* Populate delay states */
+ if ((cmd->sample_delay_h == 0 && cmd->sample_delay_l == 0) ||
+ cmd->sample_delay_h >= 6)
+ return false;
+
if (cmd->flags & CMD_START_FLAGS_CLK_CTL2) {
- uint8_t delay_1, delay_2;
+ uint8_t delay_1, delay_2 = cmd->sample_delay_l;
/* We need a pulse where the CTL1 and CTL2 pins
-* alternate states. */
-
- /* Make the low pulse shorter then the high pulse. */
- delay_2 = cmd->sample_delay_l >> 2;
- /* Work around >12MHz case resulting in a 0 delay low pulse. */
- if (delay_2 == 0)
- delay_2 = 1;
- delay_1 = cmd->sample_delay_l - delay_2;
-
+* alternate states */
+ if (cmd->sample_delay_h) {
+ for (i = 0; i < cmd->sample_delay_h; i++)
+ gpif_make_delay_state(pSTATE++, 0, 0x06);
+ } else {
+ delay_1 = delay_2 / 2;
+ delay_2 -= delay_1;
+ gpif_make_delay_state(pSTATE++, delay_1, 0x06);
+ }
+
+ /* cmd->sample_delay_l is always non-zero for the
+* supported rates */
gpif_make_delay_state(pSTATE++, delay_2, 0x00);
- gpif_make_delay_state(pSTATE++, delay_1, 0x06);
} else {
- /* Populate delay states. */
- if ((cmd->sample_delay_h == 0 && cmd->sample_delay_l == 0) ||
- cmd->sample_delay_h >= 6)
- return false;
-
for (i = 0; i < cmd->sample_delay_h; i++)
gpif_make_delay_state(pSTATE++, 0, 0x00);
--
2.7.3
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
[sigrok-devel] [PATCH 3/4] Remove bogus part of OUTPUT used for analog sampling
Since TRICTL = 0, FX2 always either pushes or pulls the CTLx pins.
Signed-off-by: Paul Fertser <fercer...@gmail.com>
---
gpif-acquisition.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/gpif-acquisition.c b/gpif-acquisition.c
index 57e852b..09a56ca 100644
--- a/gpif-acquisition.c
+++ b/gpif-acquisition.c
@@ -215,7 +215,8 @@ bool gpif_acquisition_start(const struct
cmd_start_acquisition *cmd)
if (cmd->flags & CMD_START_FLAGS_CLK_CTL2) {
uint8_t delay_1, delay_2;
- /* We need a pulse where the CTL2 pin alternates states. */
+ /* We need a pulse where the CTL1 and CTL2 pins
+* alternate states. */
/* Make the low pulse shorter then the high pulse. */
delay_2 = cmd->sample_delay_l >> 2;
@@ -224,8 +225,8 @@ bool gpif_acquisition_start(const struct
cmd_start_acquisition *cmd)
delay_2 = 1;
delay_1 = cmd->sample_delay_l - delay_2;
- gpif_make_delay_state(pSTATE++, delay_2, 0x40);
- gpif_make_delay_state(pSTATE++, delay_1, 0x46);
+ gpif_make_delay_state(pSTATE++, delay_2, 0x00);
+ gpif_make_delay_state(pSTATE++, delay_1, 0x06);
} else {
/* Populate delay states. */
if ((cmd->sample_delay_h == 0 && cmd->sample_delay_l == 0) ||
--
2.7.3
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] Analog I/O options
Hi, On Tue, Aug 02, 2016 at 06:21:01PM +, Mike Meyer wrote: > This is also important to me. One of the things I use sigrok for is capturing > the chatter between the µcu & rf module in RC transmitters. I bought a USBeeAX > clone so I could capture the relevant analog stick movement at the same time > (unfortunately, it seems that analog input isn't working). With the latest fx2lafw firmware and libsigrok the analog input should be working. At least it does for me. Use 250 kHz capture rate or more to get accurate timing. For the reference, I am testing with [1] , and all the analog notes are applicable to my device... [1] https://sigrok.org/wiki/HT_USBee-AxPro -- 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] sigrok-cli error driver fx2lafw not found
On Mon, Dec 19, 2016 at 06:12:50PM +, Ulrich, Sebastian wrote: > After installing all the required libraries I got an error using sigrok with: > sigrok-cli -d fx2lafw --samples 20 > for testing reasons. The output was: > Driver fx2lafw not found. Is that sigrok self-compiled from the sources? > I searched within the directory “/usr/local/share/sigrok-firmware/” and found > the file “fx2lafw-saleae-logic.fw”. That's firmware that's run on the LA itself, it's not the driver the error talks about. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] sigrok-cli error driver fx2lafw not found
On Tue, Dec 20, 2016 at 10:38:05AM +0300, Paul Fertser wrote: > On Tue, Dec 20, 2016 at 07:22:32AM +, Ulrich, Sebastian wrote: > > > Is that sigrok self-compiled from the sources? > > > > Yes it is. I did it as described on the homepage. > > I cloned the git repositories and compiled and installed them. > > (libserialport, libsigrok, libsigrokdecode, sigrok-cli, sigrok-firmware) > > You need to rebuild libsigrok with appropriate switches. Either do not > use --disable-all-drivers (as --enable-all-drivers should be the > default) or add --enable-fx2lafw (and the others you might need) to > ./configure invocation. Another possibility is that you might have lacked libusb-1.0-0-dev at the time you're running ./configure. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] udev rules, TAG+="uaccess" desirable?
Hi Martin, On Tue, Dec 27, 2016 at 03:38:30PM +, Martin Ling wrote: > http://sigrok.org/bugzilla/show_bug.cgi?id=665 > > In short, there is no rules file we can supply that will work for all > users on all distributions. I'm not trying to argue here but it would be useful to know what modern distros are not covered by both plugdev and uaccess combined? Having a suitable file directly in upstream might be useful for those building from the sources, I think. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com -- 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
Re: [sigrok-devel] sigrok-cli error driver fx2lafw not found
On Tue, Dec 20, 2016 at 07:22:32AM +, Ulrich, Sebastian wrote: > > Is that sigrok self-compiled from the sources? > > Yes it is. I did it as described on the homepage. > I cloned the git repositories and compiled and installed them. > (libserialport, libsigrok, libsigrokdecode, sigrok-cli, sigrok-firmware) You need to rebuild libsigrok with appropriate switches. Either do not use --disable-all-drivers (as --enable-all-drivers should be the default) or add --enable-fx2lafw (and the others you might need) to ./configure invocation. > > That's firmware that's run on the LA itself, it's not the driver the error > > talks about. > > Does this firmware has to be transferred to the logic analyzer? It'll get uploaded automatically by the driver when you first try to use it. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
Re: [sigrok-devel] [PATCH v2 libsigrok] Support earlier versions of udev in the udev rules
On Sun, Oct 21, 2018 at 08:26:20PM +0200, Guido Trentalancia wrote: > If you want sigrok to work consistently and flawlessly with all udev versions, > you have to use the patch that I posted! Thank you for the clarifications. Let's see if the maintainers are ready to encourage 666 for the device nodes. > Least but not last the GROUP setting is too distribution-specific, for > example, > "plugdev" I think exists only in Debian, so there is no point in distributing > such file. Gentoo and Debian use "plugdev". Most other popular distros switched to systemd anyway. Users and maintainers of the other systems are likely to be used to tweaking group names and permissions to their needs. -- 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] [PATCH v2 libsigrok] Support earlier versions of udev in the udev rules
Hello,
On Sun, Oct 21, 2018 at 06:20:38PM +0200, Guido Trentalancia wrote:
> -ENV{ID_SIGROK}=="1", TAG+="uaccess"
> +ENV{ID_SIGROK}=="1", MODE="0666"
Why not
ENV{ID_SIGROK}=="1", MODE="0660", GROUP="plugdev", TAG+="uaccess"
?
--
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] [PATCH v2 libsigrok] Support earlier versions of udev in the udev rules
On Sun, Oct 21, 2018 at 06:44:33PM +0200, Guido Trentalancia wrote: > 61-libsigrok-uaccess.rules > > Please consult README.devices for further informaiton about the > difference between the two scenarios (and files): Are you not fully circumventing the intent of uaccess file by setting MODE="0666"? -- 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] sigrok-cli-0.7.1 and PulseView-0.4.1 AppImage do not start because of undefined symbol: libusb_get_version Ask Question
Hi, On Sun, Jul 21, 2019 at 10:33:52AM +0300, Kiril Dimitrov wrote: > ~/temp/sigrok-cli$ make > make all-am > CCLD sigrok-cli > /usr/local/lib/libsigrok.so: undefined reference to `libusb_free_pollfds' My guess would be that you have an outdated libusb version installed in /usr/local/lib . I suggest you run make in a way to show you full linker command line to see the library linking path. -- 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] sigrok-cli-0.7.1 and PulseView-0.4.1 AppImage do not start because of undefined symbol: libusb_get_version Ask Question
On Sun, Jul 21, 2019 at 10:33:52AM +0300, Kiril Dimitrov wrote: > ./sigrok-cli-0.7.1-x86_64.AppImage > sigrok-cli: symbol lookup error: > /tmp/.mount_sigrokLM29y6/usr/lib/libsigrok.so.4: undefined symbol: > libusb_get_version "ldd ./sigrok-cli-0.7.1-x86_64.AppImage" might give additional clues too. -- 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] Feedback on Pulseview
Hello, On Tue, Oct 01, 2019 at 08:37:43PM +1000, A/Prof Chris Andrews wrote: > I have a 15" MACBOOK PRO. Does this also mean you're running macOS on it? It might require you to unload a kernel kext if it's loaded for this device for whatever reason. -- 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] Where/how to contribute an exporter
Hi, On Sun, Sep 29, 2019 at 07:11:07AM +, Marc Jacobi wrote: > configure.ac:99: warning: PKG_PROG_PKG_CONFIG is m4_require'd but not > m4_defun'd You're certainly missing at least pkg-config (build dependency). Once you install it, rerun autogen.sh and show the results please. Also check that autotools versions you have are not older than the building process specifies. HTH -- 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] Where/how to contribute an exporter
Hey Marc :) On Mon, Sep 30, 2019 at 05:23:30AM +, Marc Jacobi wrote: > I tried installing glib-2.0 which worked (saw loads of packages being > installed). Yes, you need to install libglib2.0-dev package to get all the needed development files. HTH -- 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
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
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
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
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
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
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] 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 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 seem, the second option is not suitable for modern userspace applications that are using libusb library to talk to the USB devices (it was used for the very old version years ago). Usually the best way is to "install" WinUSB (in fact, the driver is included in Windows and what Zadig does is basically assigning it to device). Unfortunately, without doing that windows (unlike all the other common OSes) doesn't allow userspace access to USB devices. -- 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] Getting firmware for Kingston LA2016
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' has no firmware > loaded! > sr: [00:01.404000] ezusb: uploading firmware to device on 2.11 > sr: [00:01.405000] ezusb: Unable to set configuration: > LIBUSB_ERROR_INVALID_PARAM Good progress. I suggest you comment out this if block: https://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/ezusb.c;h=c2d270c4f85164298f626aa7de3826bc8e1ddd80;hb=f2cd2debf9dcbf0e83ec70d8ea41d8421a400dfd#l126 This might be related to https://github.com/libusb/libusb/issues/743 Probably ez-usb devices were never properly tested on Windows. Another option would be using some other external program to upload this firmware to EZ / FX2 chip you have. -- 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] 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 the list > "Supported hardware drivers" in the output of "sigrok-cli -L". I suggest you enable more debug and send the resulting log. It should be visible what VID/PIDs are getting considered and why they're getting ignored. -- 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] 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>&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 https://sigrok.org/gitweb/?p=libsigrok.git;a=commitdiff;h=f2cd2debf9dcbf0e83ec70d8ea41d8421a400dfd , in June this year, are you sure your libsigrok is new enough? To me it looks like you're using 0.5.1 which seems to predate that commit. -- 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] New logic analyzer: Open source firmware, cheap hardware, PulseView praise and criticism
Hey, On Fri, Nov 13, 2020 at 12:59:08AM -0800, mark_at_yahoo via sigrok-devel wrote: > Also that Digi-Key's price for just the MCU itself is US$5.53 in > single unit quantities as compared to approx. $1.50 including the > crystal, connectors, LEDs, passives, board, assembly, etc. for "Blue > Pill"s direct from Chinese suppliers, or about 3x that with fast > shipping from Amazon. Please beware of fakes[0]. This page has extensive description of what's different about them, and has a special utility to test the features in question. In any case F1 family is not too appealing these days, with all the limitations, I2C bugs etc, ST has managed to produce much better (and cheaper) devices since then AFAIK. [0] https://github.com/keirf/Greaseweazle/wiki/STM32-Fakes -- 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] 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 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? I do not have this device so can't send you a log, unfortunately. I can only suggest to try a LiveCD/LiveUSB system with GNU/Linux or probably use a VM and USB pass-through and that would be the most direct way for you to see where the things go differently as you'll be able to do as many tests as needed. -- 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] Patch proposal for Kingst LA2016 driver
Hi Helge, On Sat, Jan 02, 2021 at 06:20:54PM +0100, Helge Kruse wrote: > The MXE compiler, that is used for compiling the Windows version ignores > silently this attribute. This can be verified by a simple "Hello, World" > style program. This is a perfect find! Have you tried compiling with -mno-ms-bitfield or with pragma pack? -- 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] Sigrok web page for Fluke 45 ...
Hi stuart, Thanks a lot for providing full logs, they show some interesting feature. On Sun, Jul 04, 2021 at 11:04:05AM -0500, stuart wrote: > > sr: [00:00.781527] scpi_serial: Successfully sent SCPI command: 'AUTO?'. > > sr: [00:00.989445] scpi: Got response: 'AUTVDCO?1', length 9. > > sr: [00:00.989454] fluke-45: Response to AUTO: AUTVDCO?1. We see here echo intermixed with the reply to the previous FUNC1? command. So it's "AUT" from the echo, "VDC" from the real reply to the previous command (FUNC1?), and "O?" from echo, then "1" and then "\n" likely from echo again. Of course, it's all timing-dependent but it's essential to know the echo works essentially in parallel to answering the previous request. -- 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] epidemy of unsocial messages to mailing lists (reply-to)
On Wed, Mar 24, 2021 at 03:59:11PM +, Kevin Grant wrote: > On Wed, Mar 24, 2021 at 03:37:27PM +, Kevin Grant wrote: > > Ironically, if I hit 'reply' to Gerhard's email, the response is not going > to > the list, but only to Gerhard. > > Yes, that's how it's supposed to work with mailing lists. You press > "reply" to answer the sender, and "reply all" (or "group reply") to > keep the Cc list. So everything's fine about it. > > OK, in that case my headers are wrong, because hitting 'reply' to my emails is > sending to the list. When I hit reply on your mail I'm sending to you only, so your headers seem to be fine. Using mutt as MUA here. -- 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] epidemy of unsocial messages to mailing lists (reply-to)
Hi Kevin, On Wed, Mar 24, 2021 at 03:37:27PM +, Kevin Grant wrote: > Ironically, if I hit 'reply' to Gerhard's email, the response is not going to > the list, but only to Gerhard. Yes, that's how it's supposed to work with mailing lists. You press "reply" to answer the sender, and "reply all" (or "group reply") to keep the Cc list. So everything's fine about it. -- 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] epidemy of unsocial messages to mailing lists (reply-to)
Hi Gerhard, On Thu, Mar 25, 2021 at 09:23:08AM +0100, Gerhard Sittig wrote: > On Wed, 2021-03-24 at 20:01 +0100, sig...@rkta.de wrote: > > > > Solution seems to be to configure mailman right or use > > something more sane. > > Thank you for digging this up. That answer was very helpful in > understanding the nature and the cause of the issue. Still it's > interesting why some messages are affected while others aren't. > Could not spot a pattern yet. Apparently only those with strict enough DMARC policies are affected. I've tried modifying OpenOCD devel mailing list options following [0] but there is a problem with disabling the From munging for the message coming from DMARC p=reject senders. I've filed a ticket on SF.net support system [1]. [0] https://seanthegeek.net/459/demystifying-dmarc/ [1] https://sourceforge.net/p/forge/site-support/22082/ -- 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] epidemy of unsocial messages to mailing lists (reply-to)
Hi Gerhard, On Mon, Mar 29, 2021 at 10:43:27PM +0300, Paul Fertser wrote: > On Thu, Mar 25, 2021 at 09:23:08AM +0100, Gerhard Sittig wrote: > > On Wed, 2021-03-24 at 20:01 +0100, sig...@rkta.de wrote: > > > > > > Solution seems to be to configure mailman right or use > > > something more sane. > > > > Thank you for digging this up. That answer was very helpful in > > understanding the nature and the cause of the issue. Still it's > > interesting why some messages are affected while others aren't. > > Could not spot a pattern yet. > > Apparently only those with strict enough DMARC policies are > affected. I've tried modifying OpenOCD devel mailing list options > following [0] but there is a problem with disabling the From munging > for the message coming from DMARC p=reject senders. I've filed a > ticket on SF.net support system [1]. > > [0] https://seanthegeek.net/459/demystifying-dmarc/ > [1] https://sourceforge.net/p/forge/site-support/22082/ The SF.net support team manually reconfigured the mailman settings for OpenOCD the way I have asked them in 22082. Probably you want to do the same for the sigrok mailing list and refer to that ticket. I suggest to perform all the changes you can via the configuration interface in advance before asking them for manual intervention since changing other parameters might overwrite the one you do not have direct control over. HTH -- 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
