Radioberry not working

[haywardperson]

I reinstalled my SDRBerry, without reinstalling RPI OS. I originally choose the CH1025 and my Radioberry board has the 1016.
When the SDRBerry starts it does not hang like the Pluto+ did when it was not actually connected. But I get no spectrum and if I select anything to change on the radioberry, like band the whole thing locks up. The blue power light is on, on the Radioberry board? Do I need to reinstall, OS etc, from scratch since I had already installed SDRBerry for the Radioberry 1025?
There are log entries like:
"RB-Command = 05 Commad = 00 command_data = 03000004 Mox 0
[INFO] Command sent successfull to radioberry device."

So does this indicate a handshake from the Radioberry indicating it is alive and got the command?
Thanks for any ideas.

[haywardperson]

So I have reinstalled completely from OS about 10 times. Everything works with only the sdrplay installed. I am not sure how to tell if the Radioberry is working. I have installed the Radioberry firmware on a clean build. The sudo modinfo radioberry shows information. When I do a clean installed with SDRBerry specifying the Radioberry with CH1016, it loads and starts up. There is no signal on the spectrum. It will allow me to change bands.
If I load the sdrplay drivers into a RDB primary install, the SDRbeerry will load but if I try and change sdr from the default radioberry to the sdrplay the system locks up.
So the question is if the sdrberry was not "seeing" the radioberry board it would lockup or give an error of device not found correct?
So it seems the radioberry is alive but has some other problems and should be considered a defect board.
Does this sound correct?

[haywardperson]

Going thru the logs I see the SoapyRadioberry driver getHardwareKey called and it states Hardware=v2.0-beta5 so it must have gotten that info right from the radioberry board. Since there is no other way of knowing the hardware version.

It also states the gateware version is 0.0, does that mean their is no firmware on the CH1016?

I also see the program trying to intialize the radioberry, setting freq, gain, samplerate etc. and the response is
[INFO} Could not sent command to radioberry device.

So I think the radioberry board is defective.
Unless you tell me I am misinterpreting the logs.

[paulh002]

Please share the log file

[haywardperson]

Option name: bass value: 4
Option name: fast value:
Option name: medium value:
Option name: mode value: 0
Option name: ratio value: 12
Option name: slow value:
Option name: threshold value: 0
Option name: treble value: 0
ALSA lib control.c:1575:(snd_ctl_open_noupdate) Invalid CTL pulse
2025-12-17 21:31:41 UTC
Screen resolution 800 x 480 screenRotate 0 touch_swap setting 0
Input device name: "vc4-hdmi-0"
Device is not a keyboard
Input device name: "vc4-hdmi-0 HDMI Jack"
Device is not a keyboard
Input device name: "vc4-hdmi-1"
Device is not a keyboard
Input device name: "vc4-hdmi-1 HDMI Jack"
Device is not a keyboard
Input device name: "Contour Design ShuttleXpress"
Device is not a keyboard
Input device name: "Logitech K400 Plus"
Device is a keyboard
Keyboard also has a mouse
end keyboard
Input device name: "Realtek RTL2832U reference design"
Mouse device name: "Realtek RTL2832U reference design"
Connect to input device: "CONTOUR DESIGN SHUTTLEXPRESS"
Connecting to ESP32 CAT interface 921600 baud
ESP32 CAT interface not found
TCP CAT interface listen on port 5000

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (default), Unknown error 524.

ALSA lib pcm_asym.c:105:(_snd_pcm_asym_open) capture slave is not defined

RtApiAlsa::probeDeviceInfo: snd_pcm_open (capture) error for device (default), Invalid argument.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi0,0), Unknown error 524.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi1,0), Unknown error 524.

No matching device found.
ALSA lib control.c:1575:(snd_ctl_open_noupdate) Invalid CTL pulse

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (default), Unknown error 524.

ALSA lib pcm_asym.c:105:(_snd_pcm_asym_open) capture slave is not defined

RtApiAlsa::probeDeviceInfo: snd_pcm_open (capture) error for device (default), Invalid argument.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi0,0), Unknown error 524.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi1,0), Unknown error 524.

ALSA lib control.c:1575:(snd_ctl_open_noupdate) Invalid CTL pulse
List devices:
device bcm2835 Headphones (bcm2835 Headphones) out 8 in 0

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (default), Unknown error 524.

ALSA lib pcm_asym.c:105:(_snd_pcm_asym_open) capture slave is not defined

RtApiAlsa::probeDeviceInfo: snd_pcm_open (capture) error for device (default), Invalid argument.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi0,0), Unknown error 524.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi1,0), Unknown error 524.

No matching device found.

RtApi::getDeviceInfo: deviceId argument not found.

ALSA lib control.c:1575:(snd_ctl_open_noupdate) Invalid CTL pulse
No audio input device

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (default), Unknown error 524.

ALSA lib pcm_asym.c:105:(_snd_pcm_asym_open) capture slave is not defined

RtApiAlsa::probeDeviceInfo: snd_pcm_open (capture) error for device (default), Invalid argument.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi0,0), Unknown error 524.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi1,0), Unknown error 524.

ALSA lib control.c:1575:(snd_ctl_open_noupdate) Invalid CTL pulse
List devices:
device bcm2835 Headphones (bcm2835 Headphones) out 8 in 0

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (default), Unknown error 524.

ALSA lib pcm_asym.c:105:(_snd_pcm_asym_open) capture slave is not defined

RtApiAlsa::probeDeviceInfo: snd_pcm_open (capture) error for device (default), Invalid argument.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi0,0), Unknown error 524.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi1,0), Unknown error 524.

device name = bcm2835 Headphones (bcm2835 Headphones)
: maximum output channels = 8
ALSA lib control.c:1575:(snd_ctl_open_noupdate) Invalid CTL pulse
audio output device = 129 bcm2835 Headphones (bcm2835 Headphones) samplerate 48000 channels 2
Cannot connect to 56
Cannot connect to 57
Cannot connect to 32
Cannot connect to 33
Cannot connect to 63
The framebuffer device was opened successfully.
800x480, 16bpp
The framebuffer device was mapped to memory successfully.
Input device name: "vc4-hdmi-0"
Input device name: "vc4-hdmi-0 HDMI Jack"
Input device name: "vc4-hdmi-1"
Input device name: "vc4-hdmi-1 HDMI Jack"
Input device name: "Contour Design ShuttleXpress"
Input device name: "Logitech K400 Plus"
Input device name: "10-0038 generic ft5x06 (00)"
Touch device name: "10-0038 generic ft5x06 (00)"

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (default), Unknown error 524.

ALSA lib pcm_asym.c:105:(_snd_pcm_asym_open) capture slave is not defined

RtApiAlsa::probeDeviceInfo: snd_pcm_open (capture) error for device (default), Invalid argument.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi0,0), Unknown error 524.

RtApiAlsa::probeDeviceInfo: snd_pcm_open (playback) error for device (hw:vc4hdmi1,0), Unknown error 524.

List devices:
device bcm2835 Headphones (bcm2835 Headphones) out 8 in 0
auto correction 0
samperate rx 384 samplerate tx 48 decimation 1.000000 ifrate 384000.000000
default sdr: radioberry
Loading modules... done
Checking driver 'hifiberry'... MISSING!
Loading modules... done
Checking driver 'radioberry'... PRESENT
Loading modules... done
Checking driver 'plutosdr'... MISSING!
Loading modules... done
Checking driver 'rtlsdr'... PRESENT
Loading modules... done
Checking driver 'sdrplay'... PRESENT
Loading modules... done
Checking driver 'hackrf'... MISSING!
Make device driver=radioberry
[INFO] SoapyRadioberry::SoapyRadioberry constructor called
[INFO] SoapyRadioberry::getDriverKey called
driver=radioberry
[INFO] SoapyRadioberry::getHardwareKey called
hardware=v2.0-beta5
[INFO] SoapyRadioberry::getHardwareInfo called
firmwareVersion=0.1
gatewareVersion=0.0
hardwareVersion=2.4
protocolVersion=1.58

[INFO] SoapyRadioberry::getDriverKey called
[INFO] SoapyRadioberry::getHardwareKey called
[INFO] SoapyRadioberry::getDriverKey called
[INFO] SoapyRadioberry::getHardwareKey called
[INFO] SoapyRadioberry::getHardwareInfo called
[INFO] SoapyRadioberry::getNumChannels called
[INFO] SoapyRadioberry::getNumChannels called
[INFO] SoapyRadioberry::getFullDuplex called
[INFO] SoapyRadioberry::getFullDuplex called
[INFO] SoapyRadioberry::getStreamFormats called
[INFO] SoapyRadioberry::getNativeStreamFormat called
[INFO] SoapyRadioberry::listAntennas called
[INFO] SoapyRadioberry::getGainRange called
[INFO] SoapyRadioberry::listGains called
[INFO] SoapyRadioberry::getFrequencyRange called
[INFO] SoapyRadioberry::getSampleRateRange called
[INFO] SoapyRadioberry::listSampleRates called
[INFO] SoapyRadioberry::listBandwidths called
[INFO] SoapyRadioberry::getFullDuplex called
[INFO] SoapyRadioberry::getFullDuplex called
[INFO] SoapyRadioberry::getStreamFormats called
[INFO] SoapyRadioberry::getNativeStreamFormat called
[INFO] SoapyRadioberry::listAntennas called
[INFO] SoapyRadioberry::getGainRange called
[INFO] SoapyRadioberry::listGains called
[INFO] SoapyRadioberry::getFrequencyRange called
[INFO] SoapyRadioberry::getSampleRateRange called
[INFO] SoapyRadioberry::listSampleRates called
[INFO] SoapyRadioberry::listBandwidths called

---

-- Device identification

driver=radioberry
hardware=v2.0-beta5
firmwareVersion=0.1
gatewareVersion=0.0
hardwareVersion=2.4
protocolVersion=1.58

---

-- Peripheral summary

Channels: 1 Rx, 1 Tx
Timestamps: NO

---

-- RX Channel 0

Full-duplex: YES
Supports AGC: NO
Stream formats: CF32, CS16
Native format: CF32 [full-scale=2048]
Stream args:
* Buffer Size - Number of bytes per buffer, multiples of 512 only.
[key=bufflen, units=bytes, default=64, type=int]
Antennas: ANTENNA RX
Full gain range: [-12, 48] dB
Full freq range: [0.01, 30] MHz
Sample rates range: [0.048, 0.384] MSps
Sample rates: [0.048, 0.096, 0.192, 0.384] MSps

---

-- TX Channel 0

Full-duplex: YES
Supports AGC: NO
Stream formats: CF32, CS16
Native format: CF32 [full-scale=32768]
Stream args:
* Buffer Size - Number of bytes per buffer, multiples of 512 only.
[key=bufflen, units=bytes, default=64, type=int]
Antennas: ANTENNA TX
Full gain range: [0, 15] dB
Full freq range: [0.01, 30] MHz
Sample rates range: 0.048 MSps
Sample rates: [0.048] MSps

[INFO] SoapyRadioberry::setGain called
[INFO] SoapyRadioberry::setFrequency called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 02 command_data = 0098B944 Mox 0
[INFO] Could not sent command to radioberry device.
[INFO] SoapyRadioberry::setFrequency called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 02 command_data = 0098B944 Mox 0
[INFO] Could not sent command to radioberry device.
[INFO] SoapyRadioberry::setGain called
[INFO] SoapyRadioberry::setSampleRate called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 00 command_data = 03000004 Mox 0
[INFO] Could not sent command to radioberry device.
[INFO] SoapyRadioberry::setGain called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 0A command_data = 00000074 Mox 0
[INFO] Could not sent command to radioberry device.
[INFO] SoapyRadioberry::setFrequency called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 02 command_data = 0098B944 Mox 0
[INFO] Could not sent command to radioberry device.
[INFO] SoapyRadioberry::setFrequency called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 02 command_data = 0098B944 Mox 0
[INFO] Could not sent command to radioberry device.
[INFO] SoapyRadioberry::listGains called
[INFO] SoapyRadioberry::setFrequency called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 02 command_data = 0098B944 Mox 0
[INFO] Could not sent command to radioberry device.
correction rx 0, tx 0
30 m i2c rx 21 rx 69 rx 21 rx 70 rx 16 I2C time 2
set MDA 0
set MDA 0
tx gain 0 tx phase 0 rx gain 0 rx phase 0
set MDA 0
select_mode_rx stop all threads
30 m i2c rx 21 rx 69 rx 21 rx 70 rx 16 I2C time 2
select_mode_rx start rx threads
Start AMDemodulator
multi-stage resampler
composite rate : 0.1250000000
type : decim
num halfband stages : 2
halfband rate : 1/4
arbitrary rate : 0.5000000000
stages:
[ 0, r= 0.5000000] : halfband, r= 0.5
[ 1, r= 0.2500000] : halfband, r= 0.5
[ 2, r= 0.1250000] : arbitrary, r= 0.50000000
mode LIQUID_AMPMODEM_LSB carrier 1
set filter 4
iir filter [sos]:
iir filter | sos:
b : 0.02205239, 0.04410478, 0.02205239
a : 1.00000000, -1.44515800, 0.52615058
iir filter | sos:
b : 0.02205239, 0.04410478, 0.02205239
a : 1.00000000, -1.54312110, 0.62960398
iir filter | sos:
b : 0.02205239, 0.04410478, 0.02205239
a : 1.00000000, -1.74840248, 0.84639019
iir filter [normal]:
b : 0.13571516 0.00000000 -0.13571516
a : 1.00000000 -1.72486877 0.72856969
starttime :4737
[INFO] SoapyRadioberry::setSampleRate called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 00 command_data = 03000004 Mox 0
[INFO] Could not sent command to radioberry device.
[INFO] SoapyRadioberry::setGain called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 0A command_data = 00000074 Mox 0
[INFO] Could not sent command to radioberry device.
[INFO] SoapyRadioberry::setSampleRate called
[INFO] SoapyRadioberry::controlRadioberry called
RB-Command = 05 Command = 00 command_data = 03000004 Mox 0
[INFO] Could not sent command to radioberry device.
[INFO] SoapyRadioberry::setupStream called
[INFO] Using format CF32.
default block length is set to 504 ifrate 384000.000000

[paulh002]

gatewareVersion=0.0 is not good. This indicated the gateware file is not found.
You can also check from the command line:

dmesg | grep gate

Should look like this:

[    7.825635] inside loading_radioberry_gateware function
[    7.834428] Radioberry gateware file size: 335718
[    7.834438] GPIO ready for uploading gateware...
[    9.935355] Info: gateware upload and activation succeeded

[paulh002]

The rbf file should be in /lib/firmware directry

pi@pi2:~ $ ls /lib/firmware/*.rbf
/lib/firmware/radioberry.rbf

[haywardperson]

IS there a manual process required before the Radioberry is used that loads the gateware? I assumed it would be loaded by the manufacturer or done during the code build process.

[haywardperson]

dmesg | grep gate
[6.535452] inside loading_radioberry_gateware function
[6.554738] Radioberry gateware file size: 276541
[6.554743] GPIO ready for uploading gateware

[paulh002]

This is the file for CL016, are you sure this is the correct FPGA type?

[paulh002]

I am missing the last line gateware upload and activation success

[paulh002]

If you run the install script with RDB option it should install the driver and the gateware.
But it looks like something went wrong.
You can copy the file manually

cd Radioberry-2.x/SBC/rpi-4/releases/dev/CL025
sudo cp ./radioberry.rbf /lib/firmware

or

cd Radioberry-2.x/SBC/rpi-4/releases/dev/CL016
sudo cp ./radioberry.rbf /lib/firmware

[haywardperson]

sdrberry > sdrrabbTHe radioberry.rbf is indeed in /lib/firmware
I am manually installing the gateware now.

[haywardperson]

The log looks the same. gatewareVersion=0.0 and the same failed to send commands.
So probably a bad CL016?

[paulh002]

Are you sure it is cl016 not 25? I have such a board and it is a CL025

[paulh002]

If it is a CL016 than it looks like a board issue. The boards sometimes have issues with bad solder points. Maybe a good inspection will show something otherwise return and swap the board.

[haywardperson]

I took off the heatsink and checked and it is listed as the CH1016.
I first looked with a loupe and did not see any issues. There is a ground pad on the back that did not flow well I could try and resolder it.

[haywardperson]

Wrong picture :)

[paulh002]

That sometimes helps, or measure with a scope on the gateware line if you see pulses.

[haywardperson]

Thanks so much for your assistance. I really appreciate it. I bought the radioberry from aliexpress so it may be difficult to get a new one. But I will try.
All the best
73 AL7AK

[paulh002]

No problem, I should go back to bed ... could not sleep 😊

[haywardperson]

I hope you were able to sleep and I definitely owe you a beer.

[paulh002]

Cheers!

[haywardperson]

Hello Paul. Hope you are getting some rest.
I got my new Radioberry board.
I first installed it and tried to copy the radioberry.rbf file for CL025 over but that did not work. ( the old board was CL016)
I then burned it all down and started from scratch. But when I finished it did not work until I started SDRberry with sudo.
So may be a permissions problem with some file.
Then it worked!
Now that it is working I have noticed a few glitches. Since you have a Radioberry I thought you could comment if you have seen any of these issues with your Radioberry.
Sometimes when I am tuning around the RF input just stops being processed. The spectrum just drops to zero and there are no signals. If I just change from say USB to AM then back it all returns to working.
I have trouble with contour shuttle like there is not enough horsepower with the RPI4 and it can't keep up with the movement of the Contour. It will continue to change freq when I have stopped moving the contour.
Also a question about the Radioberry Pre-amp. There is a basic nomenclature problem with these radios. Is the Radioberry pre-amp a receive pre-amp or a transmit pre-amp or both. It is clearly a TX pre-amp from the 5w output spec but does it also do receive? I looked for the schematics and I could not find them on GIthub. Is t he output of the Radioberry Pre-amp clean enough to use or did you add an output band-pass filter.
When it was installing from scratch I thought about the millions of lines of code made by so many different people all sharing and working together. It is the best use of the internet to me. Bringing people of common passions together from all over the world. to create new things. It's pretty cool.

[paulh002]

Hi, Good it works now. For the contour set the steps on 10 Hz and limit the span of the display. It is no use to step 1hz a time through 384 Khz of span. You can set the access to the radioberry device by setting the read write rights sudo chmod 666 /dev/radioberry Sdrberry saves the resample rate in the sdrberry_config.cfg file. Better remove this setting and let it be calculated again. resample_rate = {"0.501790", "96", "0"} This sometimes generates issue if a wrong value is stored. I have no knowledge of the preamps designed by Johan, I made my own. I only use the radioberry board I have added bandpass filters and a small 10Watt amp with low pass filter. This all works well. 73, Paul And Happy new year

…

On Wed, 31 Dec 2025 at 16:56, haywardperson ***@***.***> wrote: Hello Paul. Hope you are getting some rest. I got my new Radioberry board. I first installed it and tried to copy the radioberry.rbf file for CL025 over but that did not work. ( the old board was CL016) I then burned it all down and started from scratch. But when I finished it did not work until I started SDRberry with sudo. So may be a permissions problem with some file. Then it worked! Now that it is working I have noticed a few glitches. Since you have a Radioberry I thought you could comment if you have seen any of these issues with your Radioberry. Sometimes when I am tuning around the RF input just stops being processed. The spectrum just drops to zero and there are no signals. If I just change from say USB to AM then back it all returns to working. I have trouble with contour shuttle like there is not enough horsepower with the RPI4 and it can't keep up with the movement of the Contour. It will continue to change freq when I have stopped moving the contour. Also a question about the Radioberry Pre-amp. There is a basic nomenclature problem with these radios. Is the Radioberry pre-amp a receive pre-amp or a transmit pre-amp or both. It is clearly a TX pre-amp from the 5w output spec but does it also do receive? I looked for the schematics and I could not find them on GIthub. When it was installing from scratch I thought about the millions of lines of code made by so many different people all sharing and working together. It is the best use of the internet to me. Bringing people of common passions together from all over the world. to create new things. It's pretty cool. — Reply to this email directly, view it on GitHub <#90 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIOBYUFPH44OU7DU4Q4IY234EPW3DAVCNFSM6AAAAACPH5NUYSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMZYGIYDKMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[haywardperson]

Happy New year to you too.
I was using the contour at a high step rate not a low one i.e. 1khz
It is interesting that when I first changed the permissions on /devradioberry it worked.
Then I edited the sdrberry_settings.cfg and I had to reapply the permission change to get the radioberry to work.
When I removed the resample_rate entry, the radioberry did not work and when I checked it had not recalculated the resample rate. It just put in resample_rate = {""}
So I put in your values above and the next time it did recalculate the resample rate and the values were quite different.
I still have a problem where the if gain just seems to shift. I have it set and suddenly it drops and then a few seconds later it pops back up.
So far so good. Bands have been dead here but just now heard my first SSB signals on 20mtrs! :)
I think I will just have to look at the output of the SDRberry with another SDR to see if the output is clean and hence the Radioberry pre-amp has a built-in bandpass filter.
Now to get the Pluto+ working.
All the best

[haywardperson]

Just added the 12m band!!