- osmocom-sdr - lists.osmocom.org

Osmo-fl2k for Windows
by Pierre-olivier Therrien 02 Oct '21

02 Oct '21

Hy. I recently instal osmo-fl2k on Windows and the software dont open and i have a message that pthreadVC2.dll is not Found. After research, i Found the dll un the pthread folder. Where must i place the dll for macking IT work? Télécharger Outlook pour Android<https://aka.ms/AAb9ysg>

1 0

QUIT
by Karl Baisch 13 Sep '21

13 Sep '21

Please remove me from your mailing list Thanks. Karl

1 0

[PATCH] add a new option to rtl_fm to select 2nd direct sampling mode
by Doug Hammond 18 Aug '21

18 Aug '21

Hi, The USB dongle I am using requires direct mode 2 for sampling the Q branch. The rtl_fm program assumes that "direct" means mode 1. I added a 2nd option to allow to select the other mode. Patch attached. Regards, Doug Hammond

2 1

[PATCH] rtl_tcp: put new DEFAULT_* constants in defines
by Oliver Smith 18 Aug '21

18 Aug '21

Fix failures with some GCC versions: /usr/src/packages/BUILD/src/rtl_tcp.c:90:24: error: initializer element is not constant static int llbuf_num = DEFAULT_MAX_NUM_BUFFERS; Fixes: 641c22 ("rtl_tcp: Extracted some constants out of printf strings") Change-Id: Ia9e18d4c22d957f561dcdaf2657bb6d201374375 --- src/rtl_tcp.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/rtl_tcp.c b/src/rtl_tcp.c index ad930c8..89b1fb9 100644 --- a/src/rtl_tcp.c +++ b/src/rtl_tcp.c @@ -56,9 +56,9 @@ typedef int socklen_t; #define SOCKET_ERROR -1 #endif -static const char* DEFAULT_PORT_STR = "1234"; -static const uint32_t DEFAULT_SAMPLE_RATE_HZ = 2048000; -static const int DEFAULT_MAX_NUM_BUFFERS = 500; +#define DEFAULT_PORT_STR "1234" +#define DEFAULT_SAMPLE_RATE_HZ 2048000 +#define DEFAULT_MAX_NUM_BUFFERS 500 static SOCKET s; -- 2.20.1

2 1

gr-fosphor on OSX & GNURadio 3.8
by Daniel O'Connor 24 Jun '21

24 Jun '21

Hi, I'm trying to build gr-fosphor on OSX, GNURadio 3.8 & Python 3.7.10 (built from Macports) but it blows up in a swig wrapper: [ 80%] Building CXX object swig/CMakeFiles/fosphor_swig.dir/CMakeFiles/fosphor_swig.dir/fosphor_swigPYTHON_wrap.cxx.o warning: unknown warning option '-Wno-format-overflow'; did you mean '-Wno-shift-overflow'? [-Wunknown-warning-option] /Users/oconnd1/projects/gr-fosphor/build/swig/CMakeFiles/fosphor_swig.dir/fosphor_swigPYTHON_wrap.cxx:5219:14: error: no viable overloaded '=' result = gr::fosphor::glfw_sink_c::make(); ~~~~~~ ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Full build log is at https://gist.github.com/DanielO/8a75d1cc2848f773e702d788fa8275b8 I ran cmake like so: cmake -DGR_PYTHON_DIR=/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages -DCMAKE_INSTALL_PREFIX=/opt/local -Wno-dev .. I am happy to test any patches etc but unfortunately my C++/Swig skills are nonexistent :( Thanks. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum

1 0

problem to install gr-osmosdr
by alberto.alletto＠alice.it 11 Apr '21

11 Apr '21

Hi to all!I'm new on ubuntu world...but I need to install gnuradio .. I am following a guide: sudo apt-get install python3-pip sudo pip3 install pybombs pybombs auto-config pybombs recipes add-defaults pybombs prefix init ~/prefix-3.8 -R gnuradio-default source ~/prefix-3.8/setup_env.sh ....and that is all fine. Finally I installed gr-osmosdr: pybombs install gr-osmosdr but i have a problem: ... Clone in 'gr-iqbal' in corso... Configuring: (100%) [=========================================================] [WARNING] Configuration failed. Re-trying with higher verbosity. CMake Error at CMakeLists.txt:32 (find_package): Could not find a configuration file for package "Gnuradio" that is compatible with requested version "3.9". The following configuration files were considered but not accepted: /home/alberto/prefix-3.8/lib/cmake/gnuradio/GnuradioConfig.cmake, version: 3.8.3.git .... -- Configuring incomplete, errors occurred! See also "/home/alberto/prefix-3.8/src/gr-iqbal/build/CMakeFiles/CMakeOutput.log". [ERROR] Configuration failed after running at least twice. [ERROR] Problem occurred while building package gr-iqbal: Configuration failed [ERROR] Error installing package gr-iqbal. Aborting. alberto@alberto-Studio-XPS-1340:~$ How i can solve this problem ? tnx, Alberto Entire process: alberto@alberto-Studio-XPS-1340:~$ pybombs install gr-osmosdr [INFO] Prefix Python version is: 3.8.5 [INFO] PyBOMBS Version 2.3.4 [INFO] Phase 1: Creating install tree and installing binary packages: [INFO] Executing command with elevated privileges: `sudo -H apt-get -y install libhidapi-dev' [sudo] password di alberto: Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze Lettura informazioni sullo stato... Fatto I seguenti pacchetti aggiuntivi saranno inoltre installati: libhidapi-hidraw0 libhidapi-libusb0 I seguenti pacchetti NUOVI saranno installati: libhidapi-dev libhidapi-hidraw0 libhidapi-libusb0 0 aggiornati, 3 installati, 0 da rimuovere e 11 non aggiornati. È necessario scaricare 47,8 kB di archivi. Dopo quest'operazione, verranno occupati 197 kB di spazio su disco. Scaricamento di:1 http://it.archive.ubuntu.com/ubuntu focal/universe amd64 libhidapi-libusb0 amd64 0.9.0+dfsg-1 [14,5 kB] Scaricamento di:2 http://it.archive.ubuntu.com/ubuntu focal/universe amd64 libhidapi-hidraw0 amd64 0.9.0+dfsg-1 [10,7 kB] Scaricamento di:3 http://it.archive.ubuntu.com/ubuntu focal/universe amd64 libhidapi-dev amd64 0.9.0+dfsg-1 [22,6 kB] Recuperati 47,8 kB in 0s (199 kB/s) Selezionato il pacchetto libhidapi-libusb0:amd64 non precedentemente selezionato. (Lettura del database... 228510 file e directory attualmente installati.) Preparativi per estrarre .../libhidapi-libusb0_0.9.0+dfsg-1_amd64.deb... Estrazione di libhidapi-libusb0:amd64 (0.9.0+dfsg-1)... Selezionato il pacchetto libhidapi-hidraw0:amd64 non precedentemente selezionato. Preparativi per estrarre .../libhidapi-hidraw0_0.9.0+dfsg-1_amd64.deb... Estrazione di libhidapi-hidraw0:amd64 (0.9.0+dfsg-1)... Selezionato il pacchetto libhidapi-dev:amd64 non precedentemente selezionato. Preparativi per estrarre .../libhidapi-dev_0.9.0+dfsg-1_amd64.deb... Estrazione di libhidapi-dev:amd64 (0.9.0+dfsg-1)... Configurazione di libhidapi-hidraw0:amd64 (0.9.0+dfsg-1)... Configurazione di libhidapi-libusb0:amd64 (0.9.0+dfsg-1)... Configurazione di libhidapi-dev:amd64 (0.9.0+dfsg-1)... Elaborazione dei trigger per libc-bin (2.31-0ubuntu9.2)... Install tree: | \- gr-osmosdr | +- airspy | +- airspyhf | +- osmo-sdr | +- rtl-sdr | +- bladeRF | +- soapysdr | +- gr-iqbal | | | \- libosmo-dsp | +- gr-fcdproplus | \- hackrf [INFO] Phase 1 complete: All binary dependencies installed. [INFO] Phase 2: Recursively installing source packages to prefix: [INFO] Installing package: hackrf warning: nessun commit in comune remote: Enumerating objects: 31, done. remote: Counting objects: 100% (31/31), done. remote: Compressing objects: 100% (29/29), done. remote: Total 14906 (delta 10), reused 16 (delta 2), pack-reused 14875 Ricezione degli oggetti: 100% (14906/14906), 35.98 MiB | 2.53 MiB/s, fatto. Risoluzione dei delta: 100% (10859/10859), fatto. Da https://github.com/mossmann/hackrf * [nuovo branch] OTP_USB_IDs -> hackrf/OTP_USB_IDs * [nuovo branch] grf6011 -> hackrf/grf6011 * [nuovo branch] h1r5 -> hackrf/h1r5 * [nuovo branch] h1r6 -> hackrf/h1r6 * [nuovo branch] h1r7 -> hackrf/h1r7 * [nuovo branch] master -> hackrf/master * [nuovo branch] pre-release -> hackrf/pre-release * [nuovo branch] stdout -> hackrf/stdout * [nuovo branch] transceiver -> hackrf/transceiver * [nuovo tag] 2013.06.1 -> 2013.06.1 * [nuovo tag] cft-milestone-1 -> cft-milestone-1 * [nuovo tag] jawbreaker-20120914 -> jawbreaker-20120914 * [nuovo tag] jawbreaker-20121016 -> jawbreaker-20121016 * [nuovo tag] v2013.07.1 -> v2013.07.1 * [nuovo tag] v2014.04.1 -> v2014.04.1 * [nuovo tag] v2014.08.1 -> v2014.08.1 * [nuovo tag] v2015.07.1 -> v2015.07.1 * [nuovo tag] v2015.07.2 -> v2015.07.2 * [nuovo tag] v2017.02.1 -> v2017.02.1 * [nuovo tag] v2018.01.1 -> v2018.01.1 * [nuovo tag] v2021.03.1 -> v2021.03.1 Clone in 'hackrf' in corso... Configuring: (100%) [=========================================================] Building: (100%) [=========================================================] Installing: (100%) [=========================================================] [INFO] Installation successful. [INFO] Installing package: gr-fcdproplus warning: nessun commit in comune remote: Enumerating objects: 5, done. remote: Counting objects: 100% (5/5), done. remote: Compressing objects: 100% (5/5), done. remote: Total 515 (delta 0), reused 5 (delta 0), pack-reused 510 Ricezione degli oggetti: 100% (515/515), 244.33 KiB | 919.00 KiB/s, fatto. Risoluzione dei delta: 100% (287/287), fatto. Da https://github.com/dl1ksv/gr-fcdproplus * [nuovo branch] 3.6 -> gr-fcdproplus/3.6 * [nuovo branch] gnuradio3.7 -> gr-fcdproplus/gnuradio3.7 * [nuovo branch] gnuradio3.8 -> gr-fcdproplus/gnuradio3.8 * [nuovo branch] hid-usb -> gr-fcdproplus/hid-usb * [nuovo branch] master -> gr-fcdproplus/master * [nuovo tag] fcdproplus-0.1.0 -> fcdproplus-0.1.0 * [nuovo tag] v3.6 -> v3.6 * [nuovo tag] v3.7 -> v3.7 * [nuovo tag] v3.7.12 -> v3.7.12 * [nuovo tag] v3.7.2-rc1 -> v3.7.2-rc1 * [nuovo tag] v3.7_hidraw -> v3.7_hidraw * [nuovo tag] with_hidapi -> with_hidapi Clone in 'gr-fcdproplus' in corso... Configuring: (100%) [=========================================================] Building: (100%) [=========================================================] Installing: (100%) [=========================================================] [INFO] Installation successful. [INFO] Installing package: libosmo-dsp Da https://git.osmocom.org/libosmo-dsp * [nuovo branch] master -> libosmo-dsp/master * [nuovo tag] 0.4.0 -> 0.4.0 * [nuovo tag] 0.3.0 -> 0.3.0 Clone in 'libosmo-dsp' in corso... Configuring: (100%) [=========================================================] Building: (100%) [=========================================================] Installing: (100%) [=========================================================] [INFO] Installation successful. [INFO] Installing package: gr-iqbal Da https://git.osmocom.org/gr-iqbal * [nuovo branch] gr3.6 -> gr-iqbal/gr3.6 * [nuovo branch] gr3.7 -> gr-iqbal/gr3.7 * [nuovo branch] gr3.8 -> gr-iqbal/gr3.8 * [nuovo branch] master -> gr-iqbal/master * [nuovo tag] v0.37.3 -> v0.37.3 * [nuovo tag] v0.38.2 -> v0.38.2 * [nuovo tag] v0.36.0 -> v0.36.0 * [nuovo tag] v0.37.0 -> v0.37.0 * [nuovo tag] v0.37.1 -> v0.37.1 * [nuovo tag] v0.37.2 -> v0.37.2 * [nuovo tag] v0.38.0 -> v0.38.0 * [nuovo tag] v0.38.1 -> v0.38.1 Clone in 'gr-iqbal' in corso... Configuring: (100%) [=========================================================] [WARNING] Configuration failed. Re-trying with higher verbosity. CMake Error at CMakeLists.txt:32 (find_package): Could not find a configuration file for package "Gnuradio" that is compatible with requested version "3.9". The following configuration files were considered but not accepted: /home/alberto/prefix-3.8/lib/cmake/gnuradio/GnuradioConfig.cmake, version: 3.8.3.git -- Configuring incomplete, errors occurred! See also "/home/alberto/prefix-3.8/src/gr-iqbal/build/CMakeFiles/CMakeOutput.log". [ERROR] Configuration failed after running at least twice. [ERROR] Problem occurred while building package gr-iqbal: Configuration failed [ERROR] Error installing package gr-iqbal. Aborting. alberto@alberto-Studio-XPS-1340:~$

2 3

Improving the frequency precision of R820T dongles
by radio＠aijk.org 28 Mar '21

28 Mar '21

Hello, To avoid confusion, this post is about frequency errors inherent in the dongle hardware, which is quite separate from crystal drift. Having noticed that some dongles have impressive frequency stability, I did some calibration tests, and discovered (as I should have known) that the limited number length of the dongle hardware tunes to only an approximation of the requested frequency. In extreme cases the frequency error, i.e. the difference between the actual frequency and the requested frequency, can be as much as 1 ppm. To get around this limitation, I added an experimental function to librtlsdr.c that returns the *exact* frequency that the dongle is tuned to. It does this by reading internal registers, and working backwards to compute the frequency. Software that makes use of the added function can expect 1 to 2 orders of magnitude improvement in precision, when a dongle is calibrated at one frequency and then tuned to other frequencies. If people here are interested in this work, please let me know where I can post details, preferably including the occasional graph and table. Ian

1 0

gr-osmosdr: add clock_source= parameter
by Michael Loeffler 26 Mar '21

26 Mar '21

Hello, the attached patch allows to set the clock_source on uhd devices in programs like gqrx. Bye

1 1

Idea for 2021: Regular "OsmoDevCall"
by Harald Welte 25 Mar '21

25 Mar '21

Dear Osmocom community, as the pandemic continues and physical meetings are out of the question for the forseeable future, it would be a good idea to have a periodic virtual online meeting of the interested Osmocom community. I was thinking of a format where we would serve two major purposes: 1) technical talks about osmocom relevant topics - ideally current/recent developments * can be pre-recorded to avoid any problems with technical setup, streaming, ... * should ideally have a Q+A session at their initial "airing" during one OsmoDevCall 2) unstructured solicited social event (USSE) * random chat in audio (optionally video) * not recorded, obviously The recording of the technical presentation should then be permanently made available (like the presentations of our prior OsmoCon / OsmoDevCon). Not every OsmoDevCall would neccessarily need the two parts, but I think it would be great if we can make that happen. We could also have e.g. a two-weekly schedule for the USSE and a monthly schedule for the technical presentation. We'd need somebody to volunteer to "manage" the "broadcast" side of this, preferably somebody with at least some prior exposure to online events (like the c3voc). I'm using https://osmocom.org/issues/4928 to collect a tentative list of topics. Feel free to add your ideas there, as well as any comment/ feedback you may have. Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 4

Re: Announcement of "OsmoDevCall"
by Harald Welte 03 Mar '21

03 Mar '21

Hi Garret, On Fri, Feb 26, 2021 at 09:44:53PM +0000, Garrett wrote: > Thanks for tonight, was very informative happy to hear. > If its not to0 late to add stuff to the agenda I would love to > hear of any progress on sysmoOCTSIM and the various breakout boards for > M.2 modems. sysmoOCTSIM is a sysmocom product (proprietary hardware with open source firmware on the SAM3 controllers for sim card emulation), so I'm normally against "advertising" that too much in the context of Osmocom, which is an open source project. Talks about the osmo-remsim or the SIMtrace2 firmware (both open source projects) are fine, and of course they can mention compatible hardware like the sysmoOCTSIM, but only as a side-note. There's already "osmo-remsim in practice" already on the list of topics. The modem break-out boards, or in fact all of the various Osmocom OSHW projects (like SFP breakout, SFP experimenter, ...) would of course make useful additions. I've added the following entries to https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall#Future * "mPCIe and M.2/ngff modem breakout boards" * "SFP experimenter and SFP breakout boards" Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0