New Sigrok/PulseView hardware support (Siglent SDS HD, Rigol DHO...)

[qubit]

I've just been scrolling through the open pull requests on github and there is actually someone working on fixing the Siglent SDS E-series driver, awesome!
@fredo_ if you have time, could you please kindly share a compiled version of the PR247 so that we can test the changes? I'm still not able to get the building process working 

Hi @qubit,

Yes I'm aware of this PR and already proposed to merge it with mine on Sigrok Discord channel.
They are preparing a release and plan to integrate some PRs to it, Rigol and Siglent driver update PRs (245,246,247) are candidate for it: https://sigrok.org/wiki/Developers/Release_0.8.0
TBH I'm not spending more time on it until I'm sure this eventually make its way to upstream ; I moved to another project (ngscopeclient) for now.
I can try and guide you to have your build work thought, what platform are you using?

I am trying to build for Windows 11. I am using MSYS2/Mingw64 and the sigrok-native-msys2 script from sigrok-util https://github.com/sigrokproject/sigrok-util/blob/master/cross-compile/msys2/sigrok-native-msys2. I've changed a few lines in this script.
I've changed the git repository for libusb to point to the official libsusb repo's master branch, the libsikrok repo to the siglent-sds branch of mike42's repository and the repository of pulseview to the Fix/71 branch as described in the pull request PR247 https://github.com/sigrokproject/libsigrok/pull/247.
I can build pulseview sucessfully and also run it from within a Ming64 terminal.
When running pulseview from MinGW64 I get a lot of python ModuleNotFoundErrors in the console output: No module named 'math',  No module named 'binascii'. These are internal modules of python, so they shouldn't have to be installed. Is there maybe something wrong with the python installation?

When I try to run the pulseview.exe executable from within Windows I get error messages: The procedure entry point _Z20qResourceFeatureZlibv count not be located in the dynamic link library, hinting at a problem with the Qt5 dlls. I guess that when running from within MinGW64, the PATH variable points to the correct locations of Qt5Core.dll and all required dlls.
When I run the command

Code: [Select]

ldd ./pulseview.exe

I can see that Qt5Core.dll will be loaded from /mingw64/bin/Qt5Core.dll, as well as a lot of other dlls that also will be loaded from /mingw64/bin/.
How can I compile Qt5 into the pulseview executable statically, so that running pulseview.exe from within Windows does work? Did you also run into such problems?

[DirtySignal]

I don't know about compiling native using MSYS2/Mingw64 - I managed to compile using the cross mingw compile under Linux but I had to do many things that I hope I can retrace now for later use to get it all done and among that was having to create the installer after the build completed which bundles all the dependencies for Windows using makensis. It might be that you will need to do something similar. In the meantime we're hijacking this thread a little off-label...

[fredo_]

When I try to run the pulseview.exe executable from within Windows I get error messages: The procedure entry point _Z20qResourceFeatureZlibv count not be located in the dynamic link library, hinting at a problem with the Qt5 dlls. I guess that when running from within MinGW64, the PATH variable points to the correct locations of Qt5Core.dll and all required dlls.
When I run the command

Code: [Select]

ldd ./pulseview.exe

I can see that Qt5Core.dll will be loaded from /mingw64/bin/Qt5Core.dll, as well as a lot of other dlls that also will be loaded from /mingw64/bin/.
How can I compile Qt5 into the pulseview executable statically, so that running pulseview.exe from within Windows does work? Did you also run into such problems?

Yep that's "normal", I never got native build to run as a standalone exe either, it only works when launched from MinGW64 shell.
You need Linux cross compilation like @DirtySignal said to generate an installer that can work standalone.

Other option might be to use github actions from sigrok-build project: https://github.com/sigrokproject/sigrok-build/actions/

[ttelectronic]

Thanks for the work on this!  I am able to get it to work ok on the displayed data. Apologies I'm not real familiar with pulseview. I'm trying to pull data from history on my SDS824X HD, I am only able to pull the displayed data.

So I'm not sure if I'm misunderstanding this feature in pulse view, or whether its not working for this scope.

[tautech]

Thanks for the work on this!  I am able to get it to work ok on the displayed data. Apologies I'm not real familiar with pulseview. I'm trying to pull data from history on my SDS824X HD, I am only able to pull the displayed data.

So I'm not sure if I'm misunderstanding this feature in pulse view, or whether its not working for this scope.

Please see History use examples here:
https://www.eevblog.com/forum/testgear/sds800x-hd-review-demonstration-thread/msg5293747/#msg5293747