Hi!

Yes, you could modify FPGA firmware (image) to implement a digital filter. For example, take a look on how the signal averaging  is implemented in the 'mavg' component and integrated in the firmware. If the filter will always be enabled, then this would be all that is required to make it work. Vivado can be used for compiling the FPGA image.

If you want the ability for this filter to be switched on or off through the software GUI, then you would need to add a new setting option to the hardware control registers . These registers are modified through the GUI software (or Python API) and transferred from software to the hardware. After choosing a reserved (unused) register, you woud need to write a new C function in the software to control this register (again, for example, take a look at the  sfSetAverage and sfGetAverage) functions in scopefunapi.c . Then a new wxwidgets check-box would be added to the GUI and it would be used to call these hardware register modifying functions through wxWidgets.

Another option is to implement this digital filter on the host (PC), after samples are retrieved from the board. This could most  trivially be implemented in Python, using scopefun Python API to connect to the board and read the samples.

Regarding the Python module, it will be found in the "build/source" folder after successful compilation of the software. The name of the module indicates the Python version for which it was built for. For example: scopefun.cpython-310-x86_64-linux-gnu.so is for Python version 3.10. The module must be located in the same folder from which the python script will be run.

More information about using the API is available in Python API Wiki.

Hi,

it seems the issue is related to the Ubuntu 23.04 and SDL2-2.0.12, however I'm not sure about the exact reason.

I am currently working on updating the scopefun repository with newer libraries, including SDL2. The latest version from the repository should already compile fine on Ubuntu. Could you try to compile the latest scopefun version by cloning from the current develop branch from GitLab?
git clone --branch develop https://gitlab.com/scopefun/scopefun-software.git
 
If you want to change only the SDL2 sources in Release_v2.2.0, you should download SDL2 latest release-2.28.1  and replace the SDL2 files in the "scopefun-software/lib/SDL2-2.0.12" folder.

Let me know any of the above helps.

I'm still not sure why you are  getting these errors... Maybe something is broken with your Python installation and you would need to re-install Python.

Another option you can try is to use Python which is provided with MSYS2. To verify which Python version is provided with MSYS2, enter the following command in the MSYS2 MINGW64 terminal:

$ pacman -Sl | grep "python " | grep "installed"
mingw64 mingw-w64-x86_64-python 3.10.11-1 [installed]
Uninstall Python 3.9.5 from Windows completely, leaving only Python which is provided with MSYS2.

For the cmake configure step, instead of using cmake-GUI Windows application, use cmake provided with MSYS2:

cd scopefun-software/
mkdir build && cd build
cmake -G "MinGW Makefiles" -D SCOPEFUN_VERSION_MAJOR="2" -D SCOPEFUN_VERSION_MINOR="2" -D SCOPEFUN_VERSION_MICRO="0" -D SCOPEFUN_BUILD_TYPE="Release" ..

Note: cmake can be installed with pacman -S mingw-w64-x86_64-cmake

In the cmake log output you should see the following:
...
-- pybind11 v2.9.0 dev1
-- Found PythonInterp: C:/msys64/mingw64/bin/python3.10.exe (found version "3.10.11")
-- Found PythonLibs: C:/msys64/mingw64/lib/libpython3.10.dll.a
-- pybind11::lto disabled (problems with undefined symbols for MinGW for now)
-- pybind11::thin_lto disabled (problems with undefined symbols for MinGW for now)
-- Found Python: C:/msys64/mingw64/bin/python3.10.exe (found suitable version "3.10.11", minimum required is "3.9") found components: Interpreter Development Development.Module Development.Embed
-- Configuring done (123.6s)
-- Generating done (0.8s)
After that you can build ScopeFun with:
mingw32-make package

Double check that you have the following entries in your Windows Path (in this order):
C:\Users\<your_windows_username>\AppData\Local\Programs\Python\Python39\Scripts\
C:\Users\<your_windows_username>\AppData\Local\Programs\Python\Python39\
C:\msys64\mingw64\bin

Double check that you installed all the required programs in "MSYS2 MinGW 64-bit":

pacman -Su
pacman -S mingw-w64-x86_64-gcc
pacman -S git
pacman -S make
pacman -S mingw-w64-x86_64-make
pacman -S msys/automake-wrapper
pacman -S msys/autoconf
pacman -S mingw-w64-x86_64-nsis


When performing the cmake configure step (before generate step), please check if you get the following output (note the Found Python... log entries):

...
pybind11 v2.9.0 dev1
Found PythonInterp: C:/Users/Win10/AppData/Local/Programs/Python/Python39/python.exe (found version "3.9.5")
Found PythonLibs: C:/Users/Win10/AppData/Local/Programs/Python/Python39/libs/python39.lib
pybind11::lto disabled (problems with undefined symbols for MinGW for now)
pybind11::thin_lto disabled (problems with undefined symbols for MinGW for now)
Found Python: C:/Users/Win10/AppData/Local/Programs/Python/Python39/python.exe (found suitable version "3.9.5", minimum required is "3.9.5") found components: Interpreter Development Development.Module Development.Embed
Configuring done


You should install 64-bit program versions.

I'm not sure why you are getting errors at linking stage. Do you have multiple Python versions installed? If so, remove other versions. Check if Python lib folder is added to the Windows PATH variable and try to build again from a clean build folder.

If you are still getting errors, please provide complete build log.

Hi,

are you asking for tutorial regarding the digital pattern generator or AWG generator? What specifically do you mean by burst option? Both analog and digital generators always repeat the pattern at the chosen frequency.

Example files for analog/digital generator are provided in the <install_dir>/data/signal folder.

I haven't tried to compile for ARM, I'm not sure what needs to be changed to make it work.

What is the output of configure step after you replaced the config.guess file?