For the record I have been using Chris's port to 3.10 over the last couple of months and it is working to the level that suits my needs.
Rick On 2023-08-13 12:57, Chris Gorman wrote: > Hi Marcus, > > I replied to Robin, but not the list, sorry. One of the things I did in > the past (over 2 years ago) was to port gr-limesdr to gnuradio 3.9, that > work is available at https://github.com/chrisjohgorman/gr-limesdr > <https://github.com/chrisjohgorman/gr-limesdr> . I did it to try to > understand how to port something with gr_modtool and had planned to buy > a limesdr. I believe this will still work with 3.10, but without any > hardware to test out, I'm not 100% sure. > > Best regards, > > Chris > > > > > > On Sun, Aug 13, 2023 at 3:50 PM Marcus D. Leech <[email protected] > <mailto:[email protected]>> wrote: > > On 13/08/2023 14:55, robin ivetic wrote: >> Hello, >> >> I try to install gr-limesdr on arch linux true pacman, but after >> gnuradio upgrade on 3.10.7, can't do that any more, and compiling >> gr-limesdr gives me this, and files are there >> >> CMake Warning (dev) at /lib/cmake/gnuradio/GrPython.cmake:21 >> (find_package): >> Policy CMP0148 is not set: The FindPythonInterp and >> FindPythonLibs modules >> are removed. Run "cmake --help-policy CMP0148" for policy >> details. Use >> the cmake_policy command to set the policy and suppress this warning. >> >> Call Stack (most recent call first): >> /lib/cmake/gnuradio/GnuradioConfig.cmake:37 (include) >> CMakeLists.txt:77 (find_package) >> This warning is for project developers. Use -Wno-dev to suppress it. >> >> CMake Warning (dev) at /lib/cmake/gnuradio/GrPython.cmake:27 >> (find_package): >> Policy CMP0148 is not set: The FindPythonInterp and >> FindPythonLibs modules >> are removed. Run "cmake --help-policy CMP0148" for policy >> details. Use >> the cmake_policy command to set the policy and suppress this warning. >> >> Call Stack (most recent call first): >> /lib/cmake/gnuradio/GnuradioConfig.cmake:37 (include) >> CMakeLists.txt:77 (find_package) >> This warning is for project developers. Use -Wno-dev to suppress it. >> >> -- Extracting version information from git describe... >> -- Found pybind11: //include (found version "2.11.1") >> -- Configuring LimeSuite C++ Libraries... >> CMake Error at /lib/cmake/LimeSuite/LimeSuiteConfig.cmake:49 >> (message): >> cannot find LimeSuite includes in //include >> Call Stack (most recent call first): >> CMakeLists.txt:135 (find_package) >> >> I have LimeSDR-USB, and when I'm using osmosdr sink block or Soapy >> LimeSDR sink below 30MHz, I'm geting this error, explained great >> here >> >> <https://discourse.myriadrf.org/t/mcu-error-3-sxr-tune-failed-on-limesdr-usb/5303>,and >> question is more for Myriadrf >> >> <https://discourse.myriadrf.org/t/mcu-error-3-sxr-tune-failed-on-limesdr-usb/5303> >> >> MCU error 3 (SXR tune failed) on LimeSDR USB >> >> <https://discourse.myriadrf.org/t/mcu-error-3-sxr-tune-failed-on-limesdr-usb/5303> >> Hi! I wanted to check LimeGPS project, but was unable to do this. >> Right now I’m facing calibration issues when running it: Opening >> and initializing device... Reference clock 30.72 MHz Sample rate: >> 2500000.0 Hz (Host) / 2500000.0 Hz (RF) Calibrating... Tx >> Calibration: MCU error 3 (SXR tune failed) Warning: Failed to >> calibrate device: Tx Calibration: MCU error 3 (SXR tune failed) >> Setup TX stream... Creating GPS task... Using static location >> mode. xyz = 1335616.6, -4648136.6, 4144388.5 llh =... >> discourse.myriadrf.org <http://discourse.myriadrf.org> >> >> // >> >> >> MCU error 3 (SXR tune failed) on LimeSDR USB >> >> but in my case, I will get error when I use more than 11.2e6 >> bandwith, that would be reason why I tried with gr-limesdr, but >> don't know how to bypass error. >> Or maybe someone can comment error to bypass error bellow 30MHz, >> because issue is here for a long time, or did someone tried >> emulate limeSDR USB with USRP 200 >> >> Robin >> > gr-limesdr hasn't been maintained in nearly 4 years. It isn't > compatible with GR 3.10.X > >
