Menu

#12 Trouble with libiio and a pluto + sdr

1.0
open
nobody
None
2021-09-12
2021-09-08
No

First off, I commend your effort and dedication in producing the best platform for SDR I have as yet tried.

I own a pluto + sdr, have jumpered it to run as a standard Adalm Plutol,, and have the latest firmware installed (0.34) from Analog Devices. I have the damnedest time getting anything to launch with the exception of SDRangel. All other apps fail on initialization, leaving a tell-tale error in my syslog:

Sep 7 23:07:06 SEAWOLF kernel: [ 894.094181] SigDigger::Init[2426]: segfault at 60 ip 00007fdd011f463c sp 00007fdd033ef320 error 4 in libiio.so.0.19[7fdd011f1000+10000]
Sep 7 23:07:06 SEAWOLF kernel: [ 894.094191] Code: 1e fa 31 c0 39 77 60 76 0a 48 8b 47 58 89 f6 48 8b 04 f0 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 56 41 55 41 54 55 53 <8b> 47 60 85 c0 74 55 48 8b 5f 58 83 e8 01 49 89 f5 89 d5 4c 8d 74

Every program seemingly segfaults with same error in libiio.so.0.19.

Given my ignorance of the platform,, and having not found iio_info with which to test hardware operability, I initially installed several iio packages with apt from the underlying Ubuntu sources. And then discovered by total accident the awesomeness of /usr/src. I then apt purged the Ubuntu iio packages, went into /usr/src, and did a make install in the libiio dir and then a righteous ldconfig for good measure.

This is my third installation in a week: first was R15; second was R16 but filesystem went to 100% and I didn't want to bother fixing, just made a bigger partition. Never could get any app to launch.

I appreciate your effort, recommend installing iio utilities as default, and ask you what your recent pluto firmware is all about -- weighs in at double the ananlog devices one....

F.

Discussion

  • Cemaxecuter

    Cemaxecuter - 2021-09-12

    Frank,

    Thank you and welcome! I only have a plutoSDR but I'm really interested in the + version.

    So once I finally got the plutosdr i realized there was some mistakes i had made in earlier versions. What you should find is that on the release 16, at least with my normal pluto and v33 firmware, nearly everything using Soapy/Pluto works. SDRAngel has it's own build in thing and so does SDR++, so they should work too.

    What I just noticed the other day though is that within GNU Radio the pluto source/sink were messed up because I had installed some py iio thing or something according to the PySDR course material I included in DragonOS. What I ended up having to do was rename iio or something like that, change up one other thing, and now the sink/source in GNU Radio and everything else works... at least here it does. Sorry for the vague details, I'm away from my desk at the moment.

    I'm terrible at documentation, so yes, you'll find everything for the plutoSDR is already installed and I tried best I could to leave everything in the /usr/src that I had used along the way. Installing from apt could be deadly depending on what you install because there's some things I've shoe horned in via source, overwrote things here and there just to have certain things playing nice with other things. I was not aware of iio utilities, so I'll look at including that.

    I'm wondering if there's changes in the + that make it so soapy doesn't work well? Are you able to use SDR++ with it? Reason I ask, the SDRAngel guy specfically said he added Pluto+ support, so I'm wondering if there's something way different with it. I'll leave this open in the hopes we can resolve what's happening.

     
  • Cemaxecuter

    Cemaxecuter - 2021-09-12

    Forgot to mention, the PlutoSDR firmware I'm working on is based on v33 and it has the SigDigger suscli agent, rtl433, openvpn, and a few other things built it. I have it to where the PlutoSDR can do all it's own DSP and send it over to the SigDigger GUI!

     

Log in to post a comment.