Re: [sigrok-devel] cross compile pulseview for linux fails: bindings/swig/enums.i:1: Error: Unknown directive '%attribute'

Am 09.12.2024 um 18:50 schrieb Helge Kruse via sigrok-devel: Am 27.01.2024 um 18:15 schrieb Cedric de Wijs via sigrok-devel: I'm trying to cross compile sigrok for linux, in an arch linux system. My plan is to make a new user, grab MXE, and then use sigrok-cross-linux to compile puls

Re: [sigrok-devel] cross compile pulseview for linux fails: bindings/swig/enums.i:1: Error: Unknown directive '%attribute'

Am 27.01.2024 um 18:15 schrieb Cedric de Wijs via sigrok-devel: I'm trying to cross compile sigrok for linux, in an arch linux system. My plan is to make a new user, grab MXE, and then use sigrok-cross-linux to compile pulseview. Here we go: 1) Create the new user: [cedric@cedric ~]$ su Passw

Re: [sigrok-devel] Working on a new decoder - avr_updi

On 30.01.2024 23:47, Paul "LeoNerd" Evans wrote: It's quite early yet, in that it successfully parses and runs some tests on a few capture files I have of some simple cases, but I'm sure a lot of work is still needed to add more decoding of other situations and so on. It would be helpful to add

Re: [sigrok-devel] [PATCH] Revitalize MSYS2 native build

Hello Pavel, I find the build with MSYS2 very interesting. I would like to try it here, please share. The "Save" problem might be related to the change in bool StoreSession::start() introduced with commit 292b6ebc. The variable start_time is now a not initialized DateTime struct instead of a Tim

Re: [sigrok-devel] sigrok-cli output trouble

If you want to see the annotations like "TX: xxx" "RX: yyy" you should use the -A options instead of -B. The -B option creates just the binary output. See: https://sigrok.org/wiki/Sigrok-cli No other information is printed to stdout, so this is suitable for piping into other programs or savi

Re: [sigrok-devel] libsigrok PR : update HACKING

I highly appreciate both proposals. It makes the code clear and less error-prone. Best regards, Helge On 30.11.2022 16:04, fenug...@mail.com wrote: I think the HACKING file in the different sigrok projects could be updated and unified. Here is one step in that direction : (also submitted as ht

[sigrok-devel] Extend decoder search path by more than one folder

Hello, PulseView searches for decoders in the program folder in the folder %PROGRAMDATA%/libsigrokdecode and a folder specified in the environment variable SIGROKDECODE_DIR. I have two folders outside the libsigrokdecode and the program folder and want to specify both folders. But SIGROKDECODE_D

[sigrok-devel] Creating new "signals" in decoder

I have already written some decoders stacked on UART and I2C decdoers. The usual use case is to detect high level framing and add textual annotations with the detected information. Now I need a non-textual display. One of the detected information is a channel mask for 4 channels. I want to add 4

Re: [sigrok-devel] pre-assignment of channels in decoder

Am 28.01.2022 um 17:13 schrieb Uli Huber: Hi, I wonder if/how I could pre-assign channels in a decoder to avoid setting them after selecting the decoder. While I found this i.e. implemented in the „Parallel“ decoder, I was unable to transform this to non-sequential channels. I think you can

[sigrok-devel] File handling in decoder

My protocol decoder shall write some data to a file during invocation of the decode method. For that purpose I create the file once in the start method: class Decoder(srd.Decoder): inputs = ['uart'] options = ( {'id':'path', 'desc':'', 'default':'/tmp/dat'}, ) def start(self):

[sigrok-devel] Debugging stacked sigrok protocol decoder

Hello, There are several reasons for the desire to develop sigrok protocol decoders without installing the complete environment that is necessary to build sigrok, e.g. * You have an OS that is not supported as build environment. * You want to use PulseView on a PC without the build environment

Re: [sigrok-devel] Accessing protocol decoder options

e job. Best regards, Helge *From:* Ivan Wick [mailto:ivanwick+sourceforge@gmail.com] *Sent:* Monday, November 1, 2021, 8:42 PM *To:* Helge Kruse *Cc:* sigrok-devel@lists.sourceforge.net *Subject:* [sigrok-devel] Acce

[sigrok-devel] Accessing protocol decoder options

Hello, I am not an experienced Python programmer. So I'd like to ask some detail to the syntax I found in sigrok protocol decoders. I wonder about the syntax or probably syntactic sugar in the libsigrokdecode library. The sigrok protocol decoder API (https://www.sigrok.org/wiki/Protocol_decoder_A

[sigrok-devel] Hide decoder annotation rows and classes

I have a protocol decoder that generates several annotation classes in several annotation rows. There are some annotation classes that are sometimes interesting because they show some details. In most other use cases I am overwhelmed from all the details and I disable the unwanted annotations and/o

Re: [sigrok-devel] Various small pull requests to enable shared builds on MinGW64

On Wed, Mai 5, 2021 at 6:45 AM Kyle Johnson wrote: I actually built sigrok manually on the MSYS2 environment targeting MinGW64. I was able to do it successfully by targeting shared libraries for the dependencies (as there's no static Python 3 build in MinGW64). The only goofiness was trying to f

Re: [sigrok-devel] Various small pull requests to enable shared builds on MinGW64

On 04.05.2021 20:55, Kyle Johnson wrote: I've made a few fixes to enable building on MinGW64 on Windows using shared imports. Does this mean that you built sigrok in the MSYS2 environment on Windows? Or did you built it with the sigrok-util/cross-compile/mingw script for Windows? Regards, Helg

Re: [sigrok-devel] LA2016 bug fixes

Am 25.03.2021 um 16:40 schrieb Gerhard Sittig: >> Yes, the basic operation is fundamentally broken. The implementation >> uses a construct of packed structs to layout USB reports. The packed >> attribute is suppressed for some reasons in the MXE cross compile >> configuration for the whole libsigro

Re: [sigrok-devel] LA2016 bug fixes

Am 14.03.2021 um 12:50 schrieb Kevin Grant: > > I submitted a PR for the sigrok-utils LA2016 firmware extraction script > > https://github.com/sigrokproject/sigrok-util/pull/6/files > > > It works for me but if someone else could verify th

Re: [sigrok-devel] Call for testers: libsigrok drivers list and build support

Hello Gerhard, Am 05.03.2021 um 19:55 schrieb Gerhard Sittig: > This is a call for testers. Especially on those platforms which > are not exactly mainstream. That is: anything outside of one of > the popular Linux distros, which I used in a local setup. I ran this in MSYS2 on Windows 10. The make

Re: [sigrok-devel] LA2016 bug fixes

Hello Gerhard, hello Kevin, comments are in-line. Best regards, Helge Am 10.03.2021 um 14:15 schrieb Kevin Grant: > > Hello Gerhard, > > On 2021-03-08 18:25, Gerhard Sittig wrote: > >> Is the basic operation fundamentally broken, or are just not all >> of the product's features available while t

Re: [sigrok-devel] [ANNOUNCE] sigrok-cli 0.7.2 released!

Moin Uwe, hello list members, thanks for this release of the sigrok command line software. I used the --list-supported option. Unfortunately I couldn't find this device: https://www.sigrok.org/wiki/Kingst_LA2016 Is there any plan to get the supported devices (as read in the wiki) to the software

Re: [sigrok-devel] LA2016 bug fixes

Am 25.01.2021 um 19:43 schrieb Gerhard Sittig: > Can you fixup the issues in that series? I hope, I did so. > Who else had a look at these changes, or even tested it for > proper operation? I have tested it with Windows and Linux. Unfortunately I don't have a list of mailing list members with t

Re: [sigrok-devel] LA2016 bug fixes

Am 26.01.2021 um 09:53 schrieb Kevin Grant: > > On 2021-01-26 07:48, Helge Kruse wrote: > >> Am 25.01.2021 um 19:43 schrieb Gerhard Sittig: >>> On Sun, 2021-01-24 at 19:15 +0100, Helge Kruse wrote: >>>> I have recently fixed driver bugs for the Kingst LA201

Re: [sigrok-devel] Is http-service at sigrok.org down ?

Am 27.01.2021 um 09:42 schrieb Uffe Jakobsen: > Is http-service at sigrok.org down ? > I not been able to reach it the past 12 hours Corresponding to https://downforeveryoneorjustme.com/sigrok.org?proto=https it's down. Regards, Helge ___ sigrok-deve

Re: [sigrok-devel] LA2016 bug fixes

Am 25.01.2021 um 19:43 schrieb Gerhard Sittig: > On Sun, 2021-01-24 at 19:15 +0100, Helge Kruse wrote: >> I have recently fixed driver bugs for the Kingst LA2016 driver. >> I have created a pull request for you to merge. >> >> https://github.com/sigrokproject/libsigrok/p

[sigrok-devel] LA2016 bug fixes

Hi, I have recently fixed driver bugs for the Kingst LA2016 driver. I have created a pull request for you to merge. https://github.com/sigrokproject/libsigrok/pull/112 Best regards, Helge ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.

Re: [sigrok-devel] Patch proposal for Kingst LA2016 driver

Am 07.01.2021 um 21:03 schrieb Kevin Grant: > > Ray, > > FYI to extract the bitstream from USB packets I used (Windows, sorry) > Eltima Software USB Analyzer, free 14 day evaluation. > > Run it, select LA2014, start Kingst software. Select all the 4096 size > packets (INs and OUTs, so 90 frames) an

Re: [sigrok-devel] Patch proposal for Kingst LA2016 driver

Am 07.01.2021 um 19:27 schrieb Kevin Grant: > > Hello Helge, > > I have been researching the LA2016 a little to see if I can help with > the Sigrok integration. In summary, I would say it cannot work on > Linux or Windows at present. > I agree. There are at least two problems, I found. I sent a pul

Re: [sigrok-devel] Patch proposal for Kingst LA2016 driver

Am 03.01.2021 um 16:39 schrieb Gerhard Sittig: > Sorry, but I cannot see how this is "a compiler bug". Well, the C standard doesn't specify how the compiler builds the layout of structs. The GCC add an implementation specific extension with the __attribute__ to force packing of the struct. If the

Re: [sigrok-devel] Patch proposal for Kingst LA2016 driver

n|| > > On 2021-01-02 22:51, Ray Molenkamp wrote: > >> I do not have the hardware to test on, but with a "hello world" style >> program -mno-ms-bitfield fixes the struct size from 18 back to 16 >> >> --Ray >> >> On 2021-01-02 11:19 a.m., Paul Fertse

[sigrok-devel] Patch proposal for Kingst LA2016 driver

Happy new year to everyone! I use the Kingst LA2016 logic analyser and found that it doesn't work in Windows environment. There is an USB transfer that is built from a packed struct: typedef struct sample_config {     uint32_t sample_depth;     uint32_t psa;     uint16_t u1;     uint32_t u2;    

Re: [sigrok-devel] PulseView with LA2016 on Win10; ezusb: Unable to set configuration: LIBUSB_ERROR_INVALID_PARAM

ingst brand, >> whereas the unit used by the developer may have been "Jiankun" >> (guessing because that unit is described on sigrok site). >> >> https://sigrok.org/wiki/Kingst_LA2016 >> <https://sigrok.org/wiki/Kingst_LA2016> >> >

Re: [sigrok-devel] PulseView with LA2016 on Win10; ezusb: Unable to set configuration: LIBUSB_ERROR_INVALID_PARAM

Hi Kevin, I have also this Kingst LA2016 device and it doesn't work with sigrok on Windows. The interface number should be changed in protocol.h line 37, and be used in the line 505 you cited. But this change is not sufficient. The communication with the device stucks later when the IN transfer s

[sigrok-devel] Missing information in the "Supported hardware" list

Hi, The sigrok website claims to suppport a huge amount of hardware (https://sigrok.org/wiki/Supported_hardware). Unfortunately the support varies in the aspect of software version and target OS. While sigrok works perfectly with most devices, there are problems with at the one I choosed. And I do

Re: [sigrok-devel] Protocol Decoder Info

I am also unexperinced with Python and had to learn how to implement a decoder. Here are some hints that help me. Instead of using print I use the Python log system. Here are the code lines of my decoder that are related to logging. class Decoder(srd.Decoder):     options = (     { 'id': 'log

Re: [sigrok-devel] kingst-la2016 & MXE compiler - (was: Getting firmware for Kingston LA2016)

t wrote: > ...non-gcc compilers when i used "__attribute__((packed))" in that code-base. > ...i will prepare a branch from libsigrok master to implement this. > ... > On 10/28/20 3:15 PM, Helge Kruse wrote: >> This __packed__ attribute is not honored in the >>

Re: [sigrok-devel] Getting firmware for Kingston LA2016

Looks like I got an idea what's going wrong here. The sigrok software writes another USB control request as CTRL SAMPLING. The struct sample_config_t has a uint32_t member "u2" that should not be 32 bit aligned in the USB message. This __packed__ attribute is not honored in the MXE compiler. Fill b

Re: [sigrok-devel] Getting firmware for Kingston LA2016

lto:fercer...@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 her

Re: [sigrok-devel] Getting firmware for Kingston LA2016

FX2 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

Re: [sigrok-devel] Cross compile for Windows

Okay, I found the packages that include intltoolize and 7za and used apt to installed them (intltool,p7zip-full). At a first glance it looks like that the mxe-git builds completely (see build log). But the cross-compile/mingw/ build gets errors. It looks like it doesn't use the cross-compiler. The

[sigrok-devel] Cross compile for Windows

I want to try a workaround for a problem in the context of https://github.com/libusb/libusb/issues/743 For that purpose I need to cross-compile for Windows. The recommended environment is MXE (https://sigrok.org/wiki/Windows). I started with sigrok-util/README and sigrok-util/cross-compile/mingw/R

Re: [sigrok-devel] Getting firmware for Kingston LA2016

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 suppose

Re: [sigrok-devel] Getting firmware for Kingston LA2016

From: Paul Fertser [mailto:fercer...@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 "sigro

Re: [sigrok-devel] Getting firmware for Kingston LA2016

I started "sigrok-cli -L -l5 > sigrok-cli.log 2>&1". The output is attached, but there is no VID/PID info in the log. -Original Message- From: Paul Fertser [mailto:fercer...@gmail.com] Sent: Sunday, October 18, 2020 10:22 AM To: Helge Kruse Cc: sigrok-devel@lists.sou

Re: [sigrok-devel] Getting firmware for Kingston LA2016

r [mailto: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 necessar

Re: [sigrok-devel] Getting firmware for Kingston LA2016

;'s with the directory names of where you actually extracted the files to. and "path...to\KingstVIS\KingstVIS" has to point to the extracted vendor-software. flo. On 17.10.20 14:13, Helge Kruse wrote: > C:\Users\hk\AppData\Local\Programs\Python\Python38-32\python >

[sigrok-devel] Getting firmware for Kingston LA2016

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 whe

Re: [sigrok-devel] Change size of options dialog

There is an open issue: https://sigrok.org/bugzilla/show_bug.cgi?id=1429 Is anybody working on that? Regards, Helge ___ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] Compiling PulseView failed

Am 16.09.2020 um 22:12 schrieb Pičugins Arsenijs: > > Nonono, that was just an example of a command-line you could > use (as in, a better way to use apt-get), the package names are > likely wrong since I re-typed them by hand. Please use the > instructions on the page I've linked, the command I've

Re: [sigrok-devel] Compiling PulseView failed

Am 13.09.2020 um 17:11 schrieb Pičugins Arsenijs: > Hello! > > Do you *need* to cross-compile? That seems to be what you're doing. No. Not really necessary. > I've been running self-compiled Pulseview for a couple of years now. > I suggest you follow this page: > https://sigrok.org/wiki/Linux#Buil

[sigrok-devel] Performance of protocol decoder

Hi, I wrote a stack of decoders for a rather complex protocol. It consists of two layers. It decodes a network traffic. It takes about 15 seconds to decode a trace 60 seconds. It might be annoying when I want to decode a longertrace. I would like to know if there is a concept to do some kind of p

Re: [sigrok-devel] Compiling PulseView failed

Hello Soeren, I fixed the problems. Using VcXserv instead of Xming as X11 server removed the first error messages. The second message "Attach debugger" vanished after removing an old decoder. Thanks for the help. Regards, Helge Am Mo., 14. Sept. 2020 um 11:41 Uhr schrieb H

Re: [sigrok-devel] Compiling PulseView failed

um.qt.io/topic/102617/wireshark-failed-to-get-the-current-screen-resources-using-xming-ssh > for a similar case. > > Regards > -Soeren > > > > On Sun, 2020-09-13 at 18:53 +0200, Helge Kruse wrote: > > Hi Soeren, > > > > many thanks for the hint with the CM

Re: [sigrok-devel] Compiling PulseView failed

Hi Soeren, many thanks for the hint with the CMake version. I download the latest version from https://cmake.org/download/ and added the bin directory to my PATH. That fixed the problem. Now I wanted to start Pulseview with build/pulseview/build/pulseview. Now it writes "failed to get the current

Re: [sigrok-devel] Compiling PulseView failed

sudo make install* > > Did you do the 'cmake .' step? Please not that the following dot is > required. After you have checked that all dependencies are installed, > maybe start with a clean git clone of the source directory and run these > steps again? > > > > Hel

[sigrok-devel] Compiling PulseView failed

Hello, I want to compile PulseView from the Git repository. I started asking on the IRC channel #sigrok for help. But I think things are more complex and I can provide more detailed information here. And I hope I will be able to compile it on my Ubuntu 16.04 TLS. I tried to identify the require

[sigrok-devel] Change size of options dialog

There were some request as - https://sigrok.org/bugzilla/show_bug.cgi?id=183 - https://sigrok.org/bugzilla/show_bug.cgi?id=1412 that mentioned that the options dialog could be too large if a decoder has too many options or if too many decoders have been stack. So somehow a scrollbar is added to

[sigrok-devel] Patch in AVR_ISP decoder

Hallo, this is my second try to contribute to the sigrok project. I found in the wiki. "Send the decoder (preferrably as a patch against the current git HEAD of libsigrokdecode) to the sigrok-devel mailing list". So I try this here. I am working on the AVR_ISP decoder. In the first step I have r

Re: [sigrok-devel] AVR-ISP decoder

Hallo Soeren, It's suggested to prepare a sample dumps and a "unit test" where the output of the decoder is compare with a sample output. Unfortunately I have problems with the configuration of the utility runtc that actualy performs the "unit test". The ACR-ISP decoder is stacked on the SPI deco

[sigrok-devel] AVR-ISP decoder

Hello, I have needed to decode the ISP protocol for AVR controllers.I found that the decoder found in PulseView/sigrok supports only a subset of the operations. e.g. read and write of flash and EEPROM data is missing. I extended the decoder and now I can decode more of the used operations. I woul

Re: [sigrok-devel] decode() missing positional arguments

Hello Soeren, thanks for the answer. I tried to show the functions but omitted the function body. Of course there is code, that should be substituted in my mail. But I found it as a simple user error. I started the sigrok-cli with the "-P seanet" parameter to add my decoder. I forget to stack the

[sigrok-devel] decode() missing positional arguments

I think this should be a FAQ style question but unfortunately I didn't find any answer yet. I have decoder added to the directory ~/.local/share/libsigrokdecode/decoders like this class Decoder(srd.Decoder): api_version = 3 id = 'seanet' inputs = ['uart'] outputs =

[sigrok-devel] Missing glib-2.0 while building sigrok

Hi, I switched to Ubuntu and tried to build sigrok as described here: https://sigrok.org/wiki/Building I thaught I installed the prerequisites with "apt install", but I get an error: [many lines omitted] checking for jni.h... no checking for LIBSIGROK... no configure: error: Package requirem

Re: [sigrok-devel] Develop and debug decoder(s)

Am 08.03.2020 um 19:50 schrieb Gerhard Sittig: > The difference may be that on Linux the application uses the > system's Python runtime, and thus has locally installed modules > available. This may not be the case for the binary Windows > installation that you appear to run, but this is just a gues

Re: [sigrok-devel] Develop and debug decoder(s)

Am 04.03.2020 um 19:15 schrieb Gerhard Sittig: > On Wed, 2020-03-04 at 17:19 +0100, Helge Kruse wrote: >> How can I setup a debugger (I hope WinPDB, pdb would also be okay) on >> my Windows 10 PC? >> How can I attach the debugger to the running PulseView process, or can >&g

Re: [sigrok-devel] Develop and debug decoder(s)

Am 04.03.2020 um 17:32 schrieb Inessa Kavalenka: > Hi Helge! I'm not sure if it works on Win10, but for debugging on ubuntu I > use gdbgui. > Hi Inessa, thanks for response. What is your development process of sigrok/PulseView decorders with gdbgui? If I get gdbgui running on Windows, how can I

[sigrok-devel] Develop and debug decoder(s)

Hi, after writing my first decoder half a year ago I want to start with a new decoder. The documentation pages - https://sigrok.org/wiki/Protocol_decoder_HOWTO - https://sigrok.org/wiki/Protocol_decoder_API show some help. But I feel uncomfortable with this alone. I hope that digging in my decode

[sigrok-devel] Wiki improvement

Hi, In the Protocol_decoder_HOWTO page we can read: On Linux systems, this name follows the XDG base directory specification, which by default resolves to ~/.local/share/libsigrokdecode/decoders. It would be useful to add information for Windows 10 operation system. I propose this: On Windows s

Re: [sigrok-devel] Problem with new LHT00SU1

timing problem - when it > isn't working properly, it will enumerate on the USB bus, but will > disconnect as soon as sigrok tries to download firmware to it. > > On Sat, Sep 21, 2019 at 6:03 AM Helge Kruse wrote: > >> You need to install the WinUSB driver for the device

Re: [sigrok-devel] Problem with new LHT00SU1

You need to install the WinUSB driver for the device. For that purpose you will use Zadig program what has been installed with sigrok. Windows must not display it as "unknown device" after successfully installing WinUSB for it. Best regards Helge Patrick Dorion schrieb am Sa., 21. Sep. 2019, 0