Need Help with AURSINC Beta 5 - 10CL025 Radioberry

[Sherlock NICE]

Hei folks,

I need help with my Hamgeek/Aursinc Radioberry board. I'm only getting a 0-level line (-100dB) in piHPSDR, without any noise. I'm running the board on a Raspberry Pi 5 with the V5.13 image and the appropriate firmware for the C025. I regularly get an error message: "Error 11 reading frame from radioberry device" in the Radioberry console after starting piHPSDR. "ls -l /dev/radioberry" "lsmod | grep radioberry" and "dmesg | grep radioberry" produced the following outputs.

The board works fine with the Juicy board (AURSINC) under Windows, with acceptable sensitivity.

[pa3gsb]

Hi,

Initilisation of the raspberry pi and radioberry is looking good.

Your remark regulary does this mean that there are also attempts that the radio starts without issues?

I do only see many starts in the log ; is there any differenct when using the localhost (127.0.0) device when starting.

Which config are you using in pihpsdr?  sample rate? number of rx channels? do you have PS switched on ?

Besides the setup by the image there is a rpi firmware ; may be you need to update this as well?

sudo rpi-eeprom-config

Please let us know

Johan

PA3GSB

Op dinsdag 21 april 2026 om 21:31:17 UTC+2 schreef pif...@gmail.com:

[Sherlock NICE]

Dear Johan,

No. There wasn't a single attempt where the radio started normally and received signals.

The log in the terminal only simulated a single start:

1. After "sudo radioberry" in the console,

2. piHPSDR was started, which in turn generated all the messages in the previously started console ("sudo radioberry") after the message "radioberry starting packet tx part".

3. The signal line in piHPSDR remained unchanged at -100dB the entire time.

4. It makes no difference whether piHPSDR is started on 127.0.0.1 or the manually configured IP address.

I've attached the piHPSDR settings in screenshots.

It would be great if you could find the error.

73, de Alex (OE9PAV)

[pa3gsb]

Hi Alex,

Sorry i sent the wrong command  for firmware update.

This is the right command and the response of my pi-5

pi@radioberry:~ $ sudo rpi-eeprom-update
BOOTLOADER: up to date
   CURRENT: Mon  8 Dec 19:29:54 UTC 2025 (1765222194)
    LATEST: Mon  8 Dec 19:29:54 UTC 2025 (1765222194)
   RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2712/default)
            Use raspi-config to change the release.

Please reboot and try again.

Another question which was not good visible; are you a direct connection between rpi and rb ? no use of flat cable?

Furthermore io pin bcm pin 25  (https://github.com/pa3gsb/Radioberry-2.x/wiki/GPIO-RPI---Radioberry)

is important for the statemachine to get going which seems an problem in your setyup:

running pihpsdr at 384K

i polled the pin 25:

pi@radioberry:~ $ pinctrl 25
25: a7    pu | lo // GPIO25 = PIO25
pi@radioberry:~ $ pinctrl 25
25: a7    pu | lo // GPIO25 = PIO25
pi@radioberry:~ $ pinctrl 25
25: a7    pu | hi // GPIO25 = PIO25

Please let us know how it looks like?

73 Johan

PA3GSB

Op donderdag 23 april 2026 om 22:25:36 UTC+2 schreef pif...@gmail.com:

[Sherlock NICE]

Dear Johan, 

Bootloader is up to date but ...

you've pointed me to the crucial problem. Great, thank you so much. 

I'm using the Pironman 5 case from SunFounder. This uses an IO Expander HAT (picture attached). This in turn uses some Raspberry Pi GPIO pins (GPIO 6, 10, and 13). I removed all the jumpers so these pins were no longer used, and then the RadioBerry finally started up and received signals. 

So I still don't have functionality for an IR receiver, two controlled fans, and an OLED display—but you can't have everything. :-)

I'll now investigate in detail which pin was ultimately the culprit. 

Thanks again... 

73 de Alex (OE9PAV)

[pa3gsb]

Hi Alex

Tnx for the feedback. 

I think gpio 10 is the main problem...this pin is used to send commands via SPI to control the radio. That is why i suppose the data stream doesnot start.

Great work!

Enjoy the radio.

73 Johan

PA3GSB

Op zaterdag 25 april 2026 om 19:17:22 UTC+2 schreef pif...@gmail.com: