cariboulite
cariboulite copied to clipboard
cariboulabs
SDR++ SPI
Hi, I get theses errors when loading SDR++. I run the SoapyUtil and it seem to read the CaribouLite just fine.
running Pi 2 W
Any suggestions ?
I am going to run the Cariboulite Untility again and look at more closely to see if there is an issue.
then again, it could be a SDR++ issue too.
Didn't try SDR++ yet, is it possible to convince it using the CaribouLite as remote device even on the same machine? Something along the lines of
remote=127.0.0.1, driver=remote, ...
This way I believe SoapySDRServer takes over which is - normally - running as root anyway.
I am running SDR++ server mode on the Pi with the SDR++ client on a Windows box. It is running SoapySDR inside. This combo works very well since the CPU utilization on the Pi is only around 10%. I can run the sdrpp client on the Pi also (still in sdrpp server mode), audio tends to chop as the CPU is near 90-100%.
When I run SoapySDRServer and the sdrpp in SoapySDR mode, it connects OK but I do not get any audio on the Pi. Other programs like GQRX and Cubic SDR do, though CPU is very high and starts to chop. Running sdr++ on the windows in SoapySDR mode, it connects and gets choppy audio and spectrum is jus a small center hump.
While verifying the above just now, I got similar errors as the original post after I had been running the hardware straight for a week while out of town then working it hard today including several reboots. Rebooting did not clear it. I powered it off and then all came up clean again. I do run SoapySDRServer and sdrpp -server with sudo. For the clients it is not needed.
I have been running sdrpp, gqrx, OpenWewbRX, sdrangel, and CubicSDR in various combos of local and remote with a mixed bag of results. I have not got all combos runnig yet, but close. So far SDR++ in server mode running remote here has been very good.
For OpenWebRX (via SoapySDR), it works great on the RTLSDR dongle as most programs do. It sees the CaribouLite, but when trying to open it, it fails and removes it from the list of devices leaving only the RTLSDR dongle working. I was 5000miles away and listing to home radio over my cell phone just fine otherwise.
Update, I now have OpenWebRX working on the CaribouLite. It required some specific settings for SoapySDR I had missed. This is covered in #90 .
So for my situation, SoapySDR seems to work fine for local apps, but I am having trouble via SoapySDR remote, at least from my Windows box. SDR++ Server has been working great also on Pi4B 64bit. I run both SoapySDRServer and sdrpp --server with sudo.
@stevewa2066 is there any updates? I am struggling with the same issue. I also noticed when I run
lsmod | grep smi
I only get :
bcm2835_smi 20480 1 bcm2835_smi_dev
instead of :
bcm2835_smi_dev 16384 0 bcm2835_smi 20480 1 bcm2835_smi_dev
I have tried it with both the @konimaru fork and the master branch.
I'm sure that the missing smi_dev has to do with this issue, but I don't know how to remedy it.
Updated, reply earlier form my phone was incorrect.
Check out issues #104 and #66. In my case the missing entry was due to kernel header version mismatch.
I updated to the latest RPi. header version changed. uname -r gives 6.1.21-v8+. I also switched to the main branch using fork https://github.com/konimaru/cariboulite. Got the missing smi device issue. Version headers were correct. In install.sh, I added sudo in front of the cmake line and the make install line in the #4 section per below and that seemed to fix the issue for me as it has earlier. Rebooted. working correctly now.
printf "${CYAN}4. Main software...${NC}\n" cd $ROOT_DIR mkdir -p build && cd build sudo cmake $ROOT_DIR/software/libcariboulite/ make sudo -u root make install
Was only getting 1 line before. pi@raspberrypi:~/projects/cariboulite $ lsmod | grep smi smi_stream_dev 20480 2 bcm2835_smi 20480 1 smi_stream_dev