Replies: 3 comments 1 reply
-
On Pi 3B with DragonOS: you can install from the develop_R1 branch ( Do necessary reboot - as a result the But then I had the "couldn't open smi driver file '/dev/smi'" issue - which occurred if I do I've just tried P.S. BTW, lsmod | grep smi gives me this:
P.P.S. So, for develop_R1 I keep getting "couldn't open smi driver file '/dev/smi'" issue. |
Beta Was this translation helpful? Give feedback.
-
Tried with a fresh install of DragonOS Beta33 on Pi4 model B the main branch of Konimaru - still have the same issue. But I have a problem with kernel extension compilation, apparently:
Also I tried adding sudo to cmake + make steps on "Main software" because it was writing errors about lack of access. It helped with no access issue - but instead I get SMI errors
P.S. Damn - it's not finding gcc-13. And I can't install it - doesn't know that package. Let me do apt update/upgrade and retry...
I wonder why does it even want gcc-13? What's wrong with gcc version 11?
P.P.P.S. Fixed the Kernel module compilation error with these changes:
Also tried However, the errors about module insertion remain:
But, cariboulite_test_app works. At least I can toggle some LEDs and stuff - not sure how to check if it actually does something. SDR++ though sees Caribou and seems to work (supposedly - I wasn't able to listen to any FM radio though so far, I only get noise) - but only if I run it with sudo. Otherwise it's not showing SoapySDR |
Beta Was this translation helpful? Give feedback.
-
Ok, better way to do this on Pi4: Get DragonOS Beta 32 - not 33. This has older Kernel, which doesn't require manual fixes in the code to compile. But use the Konimaru repo main branch - official CaribouLite develop_R1 compiles, but doesn't work (errors about SMI module and then timeouts). Maybe I should also try main branch of the official repo, but for Konimaru on DragonOS beta 32 it compiles no issues - the only thing I modified was to remove root check from install.sh, correct path to config.txt to /boot/firmware/config.txt instead of just /boot/config.txt, and then I ran install.sh with sudo - and it all worked fine. The capture software seems to work. The only problem for me is that I can't actually get any reception. On HiF receiver I always get a hump in the middle of the graph in SDR++ - despite chosen frequency. On Sub1GHz frequency I get pretty much nothing, not even that PRM 446 radio. Something is maybe wrong with the hardware itself - not sure. P.S. Ok, I see that latest commit to the main branch (hash |
Beta Was this translation helpful? Give feedback.
-
Apologies that I have not been over all the comments and this may be already well known but after a lot of struggle here are my notes having managed to get the thing working. Also, this is a memory dump while I still remember it all so probably a bit too verbose but there you are!
First off, I never succeeded on a Pi 3B. No matter what I tried I got nowhere - I never got the driver. So this is not particularly scientific as I redeployed a Pi 4...
Next, I never managed to get past the kernel issue when using Raspberry Pi OS on the Pi 4 (specifically the 64 bit Bookworm one)
Where I succeeded was with DragonOS on the Pi 4 (I even had issues with DragonOS on the Pi 3B - it never opened ssh for some reason but did on the Pi 4)
My method was this:
Install DragonOS and to an apt update / apt upgrade cycle (lots to download) and reboot.
Using https://github.com/konimaru/cariboulite get and install the software
This failed to complete with code errors.
Edit two source files:
cariboulite/software/libcariboulite/src/CaribouLiteCpp.cpp
and
cariboulite/software/libcariboulite/src/CaribouLite.hpp
Strip out all occurrences of "apt" and "depmod" in install.sh (so it doesn't do them all again) and re-run install.sh. It ran through fine and gave me a test menu.
Edit /boot/firmware/config.txt and set these as this:
#dtparam=i2c_arm=on (commented out)
#dtparam=spi=on (commented out)
dtparam=i2c_vc=on (line inserted)
dtoverlay=spi1-3cs (line inserted)
Reboot.
I now had the driver - "lsmod|grep smi" showed this, and "/proc/device-tree/hat" now exists - I never had these before with any of my iterations.
And it works. Running "sudo SoapySDRUtils --find" succeeded, running "sudo ./cariboulite_test_app" all looks good (sorry I forgot where that is!), and, finally running "SoapySDRServer --bind" and running CubicSDR on my Mac and it finds the CaribouLite. Thus far I have left it on a local radio station for several hours and it has not crashed.
Hope this helps someone.
Beta Was this translation helpful? Give feedback.
All reactions