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
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
---
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
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
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
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
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,
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
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)
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
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
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
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
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
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
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
>
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
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
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.
> &
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
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
>
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
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'
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
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
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
>
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?
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
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:
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
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
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
>
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 us
33 matches
Mail list logo
