Latest RPi4B image crashes after install of CubicSDR
w0dz opened this issue · comments
Latest RPi4B image crashes after install of CubicSDR
Using this image:
2022-09-22-raspios-bullseye-armhf.img.xz
OS wakes up fine after above install. Install order is
SDRPlay API (rebooted after)
SoapySDR (tested connection to RSP1A, works)
LiquidDSP
WxWidgets 3.1.5
CubicSDR
Whole installation takes about 2 hours. On completion, script reports that CubicSDR will show up in the "Other" portion of the drop-down. On reboot, Linux crashes with a lot of blather that I can't paste here. It just had a lot of problems.
Brian
Is there any way to install CubicSDR on a Raspberry Pi 4B without going through all these compile steps?
I have an SDR radio image for Raspberry Pi.
There are instructions to build a system and there are Raspberry Pi 4 images pre-built.
https://www.radiosrs.net/tech.html
Let me know it you get it working.
I was unaware that there was a newer version of Raspberry Pi4B. What is the difference?
Mine is a Raspberry Pi 4B Rev. 1.4 and the procedure works on it. I often find that when people have trouble with my procedure, they did something different than what is specified in the procedure.
I don't actually have a script, but a procedure. It works with my Raspberry Pi 4B Rev. 1.4. The built OS image also works on a Raspberry Pi 3, which is underpowered for some of the applications.
I have built CubicSDR many times, so the problem is deeper than the scripts and procedures. Details about what went on are necessary.
raspios_arm64-2022-09-07 has a package for an older CubicSDR version 0.2.5. You can try that.
There is a problem with liquid-dsp Version 1.5.0 that I posted here. #976
Select an older version with git checkout v1.4.0
Does the build complete successfully? Did you install all of the many prerequisites? Which version of wxWidgets?
What are the symptoms other than just the image crashes?
I don't like the filters in CubicSDR. Signal rejection from the sideband opposite from the one you are using is poor.
What version of CubicSDR are you trying to build? CubicSDR - v0.3 does not exist and 0.2.7 is the latest.
Are you using a 64-bit OS or a 32-bit? SDRplay_RSP_API-ARM32-3.07.2.run is not appropriate for a 64 bit OS. It could crash your system.
CubicSDR was recently updated, probably v 0.2.6a to allow it to work with WxWidgets 3.1.5. Older versions won;t work with it.
I cannot use the SDRplay v0.7 image either. I did get v0.6 to work, but there are so many things it doesn't have and they are so out of date so I build my own. The picture of the boot crash did not make it into your post.
Saying that my procedure doesn't work doesn't help because it does work. I need to know what doesn't work.
I feel confident that my procedure will work on your Raspberry Pi since most of the code is built on your system, but you have to follow all of the instructions. I don't see anything that can cause it not to boot.
Again, what version of RPI do you have? It shows when you type sudo raspi-config. I can still use the latest OS.
I make a backup of my SD card on my Windows laptop and use winzip to make an archive. There are options in the imaging program that doesn't save the unused part of the disk. I have a procedure I can share.
Try this before you install soapysdr.
sudo apt install cubicsdr
It will also soapy, etc. but it's old.
Good move making a backup image. Make one every time you make progress. Restore it if you broke it.
None of this stuff has anything to do with the boot files. Unless you are doing something that you aren't talking about, the trouble lies elsewhere. Clearly something is changing these protected files.
Are you logging is as the root user?
From:
https://www.riscosopen.org/wiki/documentation/show/Software%20information:%20Raspberry%20Pi:%20Firmware
/boot/start4.elf – The Pi 4 GPU firmware. Forms a matched pair with fixup4.dat
/boot/fixup4.dat – Additional code for the Pi 4 GPU. Forms a matched pair with start4.elf
If you copy working copies to a USB drive and can mount your SD card in a USB programmer, you can boot on a working system and try to copy them back to see if it fixes them. Maybe copy the whole /boot directory.
In your case, try copying /boot from another working SD card to the non bootable one mounted in a USB programmer.
The most likely thing to change these files is an update, but it should get the right ones.
Does
sudo apt update
sudo apt upgrade
cause this boot problem?
v0.3 is the script version.
I see a BIG problem with the scripts in that they compile with "make". "make -j4" will compile many times faster, but make sure you have the heat sinks installed!
Use 4buildWidgets_3.1.5.sh to install Widgets instead of 4buildWidgets.sh. You are getting the latest version of CubicSDR, which needs 3.1.5.
3buildLiquidDSP.sh installs the latest version 1.5.0 of liquid-dsp. CubicSDR does not work properly with liquid-dsp Version 1.5.0
They don't install RtAudio. CubicSDR uses this. It is listed on the CubicSDR github page.
Try CubicSDR before you reboot.
Still nothing to do with boot files.
It looks like you did not try the procedure on my web page. I follow it when I build a new system.
See: https://www.radiosrs.net/tech.html
The system installation starts under Raspberry Pi OS Bullseye 32-bit installation...
This installs the operating system, API, Soapy, etc. You can skip the HackRF and RTL-SDR sections.
Installing drivers for the SDRplay RSP1A, HackRF One and RTL-SDR on a Raspberry Pi with Raspberry Pi OS
Then install hamlib from Installing utility software on a Raspberry Pi
Then go to Installing SDR applications on Raspberry Pi OS.
It uses make -j4 to greatly speed up the compile.
Or just download my 32-bit Raspberry Pi OS Debian Bullseye disk image. However, I'm worried it won't work on your RPI. I would really like to know, though.
I tried one of my images on a RPI 3 and it booted!
Thanks! I'm relieved for you!
Have a look around on my web site. There are a lot of cool applications and utilities.
If I can't receive or decode it, I want to know how.