DL1YCF PIHPSDR 2.6 release.

179 views
Skip to first unread message

SNAIL

unread,
Oct 28, 2025, 12:38:02 AM (8 days ago) Oct 28
to Radioberry
Anybody has tried new PIHPSDR release 2.6 with Radioberry? I have it compiled with GPIO on or off but have red line on the screen.IMG20251027194947.jpg

Negativ Zero

unread,
Oct 28, 2025, 4:06:28 AM (7 days ago) Oct 28
to SNAIL, Radioberry
Yes...on me the same

uto, 28. lis 2025. 05:38 SNAIL <snailex...@gmail.com> je napisao:
Anybody has tried new PIHPSDR release 2.6 with Radioberry? I have it compiled with GPIO on or off but have red line on the screen.IMG20251027194947.jpg

--
You received this message because you are subscribed to the Google Groups "Radioberry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to radioberry+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/radioberry/9c9849f9-de83-4e1f-b170-1479a3d42690n%40googlegroups.com.

Negativ Zero

unread,
Oct 28, 2025, 4:18:14 AM (7 days ago) Oct 28
to SNAIL, Radioberry
WITH putty analize pihpsdr...it says: old_protocol_audio_samples:output burger overflow!!

uto, 28. lis 2025. 05:38 SNAIL <snailex...@gmail.com> je napisao:
Anybody has tried new PIHPSDR release 2.6 with Radioberry? I have it compiled with GPIO on or off but have red line on the screen.IMG20251027194947.jpg

--

SNAIL

unread,
Oct 28, 2025, 8:53:08 AM (7 days ago) Oct 28
to Radioberry
Yes. IMG20251027195200.jpg

Negativ Zero

unread,
Oct 28, 2025, 9:38:11 AM (7 days ago) Oct 28
to SNAIL, Radioberry
expect from dl1ycf to resolve that isue!
best 73 
9A3RU

SNAIL

unread,
Oct 28, 2025, 7:41:15 PM (7 days ago) Oct 28
to Radioberry
Rolled back to 2.5, 2.4. The problem still exists. I think it's newly released Legacy 64 Bookworm PI OS. Nothing older available from PI Imager.

Joey G. (Bonehead)

unread,
Oct 28, 2025, 11:57:12 PM (7 days ago) Oct 28
to Radioberry
I've done a few fresh installs of Bookworm but only using 2.5 or lower.  No fresh install issues.  Maybe the roll back isn't replacing all files?

Negativ Zero

unread,
Oct 29, 2025, 2:23:52 AM (7 days ago) Oct 29
to Joey G. (Bonehead), Radioberry
Yes,agree... 2.5...have it before.wkd perfect,but,can't find anymore.
Regards!

Negativ Zero

unread,
Oct 29, 2025, 4:33:22 AM (6 days ago) Oct 29
to SNAIL, Radioberry
Friend, i'm resolve that issue with m0aws uplate.Go on site,find uplate,download,and execute.....all working fine.

Negativ Zero

unread,
Oct 29, 2025, 5:57:09 AM (6 days ago) Oct 29
to SNAIL, Radioberry
Then on imager,and all new...have--another.....64 bit full....3.1 Mb

sri, 29. lis 2025. 00:41 SNAIL <snailex...@gmail.com> je napisao:

Yado-san

unread,
Oct 30, 2025, 12:23:14 PM (5 days ago) Oct 30
to Radioberry
Hi,

I have also seen that the latest pihpsdr v2.6 does not work with RadioBerry. (Pi-OS:bookwarm and trixie)

The cause has not yet been analysed, but pihpsdr v2.5 works on both RPI4 and RPI5.
So i'v been uploaded v2.5 to my directory below. commited:8cb1c10
Please use this if required.
  https://github.com/hish8612/pihpsdr/

pihpsdr_v25a.png

pihpsdr_v25b.png

Note:
The pihpsdr version maintained by Christoph DL1YCF supports Radioberry since March, so it will work on RPI4 even with GPIO=ON.
However, for the RPI5-specific Gateware75.0, the GPIO pins for the key paddle have changed. Therefore, when compiling for RPI5 (GW75.0), please set GPIO=OFF.
-> The compilation options in the Makefile are GPIIO=ON, AUDIO=PULSE.


Yado-san, jg1twp


SNAIL

unread,
Oct 30, 2025, 1:27:38 PM (5 days ago) Oct 30
to Radioberry
Thank you Yado-san. You are my savior. 2.6 is working but only with GPIO- off compiled. All changes for Radioberry CW you and others were talking before is in release but for some reason PIHPSDR doesn't recognize that is Radioberry in use. The PDF manual says
 "However, two GPIO lines are actually available,
namely GPIO14/15for first-generation RadioBerries (with firmware versions
smaller than 73.2), and GPIO17/18 for second-generation ones (with
firmware versions 73.2 and larger). Therefore, if piHPSDR is compiled with
GPIO support and detects a RadioBerry “hat” from the presence of the special
device file /dev/radioberry, then it enforces the No Controller GPIO
choice and only uses the two available lines for CWL/CWR, so one can attach a
paddle to the two lines and use the iambic keyer built into piHPSDR."
Hard to figure out what is wrong when new OS and new release come together.

SNAIL

unread,
Oct 30, 2025, 7:50:57 PM (5 days ago) Oct 30
to Radioberry
I'm back with report how it's going. 
Installed Yado-san PIHPSDR 2.5 as it compiled GPIO -on, MIDI, PULSE AUDIO. Everything is good except no CW side tone and hanging up CW transmission from pin 5 CN301, pin 6 sometime doesn't react at all. Pin 14 straight key is OK, pin 13 PTT is OK
Recompiled PIHPSDR with ALSA AUDIO. CW side tone is working OK, pin 6 (dot) not working. CW dot now is on pin 14. CW dash is still on pin 5. Don't have paddle ready to check it but looks to me like dashes sending speed is much slower than dots speed, will check it later. 
Message has been deleted

Jatteau Marc

unread,
Oct 31, 2025, 1:33:29 PM (4 days ago) Oct 31
to Radioberry
Hello everyone.
For your information, everything is working on my end.
However, I install PiHPSDR V2.6 first and RadioBerry afterward.
I don't know if this makes a difference, but it works for me.

73 F6GKG

Le vendredi 31 octobre 2025 à 11:43:43 UTC+1, Yado-san a écrit :
Hi SNAIL, Group

You're right! :)

>> PIHPSDR doesn't recognize that is Radioberry in use.

I looked into this issue where pihpsdr_v2.6 does not works with GPIO=ON.
It looks like pihpsdr_v2.6 isn't recognising radioberry.

pihpsdr_v2.6, setting GPIO=1 causes conflicts with GPIO pins, so it doesn't work.
but.. I'm unsure where I should make the change.

Result:
  for GW=73.3, the correct GPIO for the key paddle is the following,
    CWL_LINE = 17;
    CWR_LINE = 21;
  but the default pin configuration was being used in pihpsdr_v2.6.
    CWL_LINE = 5;
    CWR_LINE = 6;

  Therefore, it appears to conflict with Radioberry pins, preventing operation.
  As v2.5(Oct.11) works correctly, it is thought that a later modification in gpio.c or radio.c caused this degradation.

Current action:
 _With compile with the GPIO=0 compile option. (m0aws's script is also  GPIO=0)
 _Or, temporarily modify pihpsdr/src/gpio.c as bellow. and GPIO=1

< v2.6, using modified pihpsdr/src/gpio.c >
pihpsdr_v26a.png
pihpsdr_v2.6 works
pihpsdr_v26b.png

Modify pihpsdr/src/gpio.c :  
 Line.810-
  case NO_CONTROLLER:
  default:
    //
    // GPIO lines that are not used elsewhere: 5,  6, 12, 16,
    //                                        22, 23, 24, 25, 27
    //
    //
    CWL_LINE = 17;   // Force radioberry(gw73.3) GPIO pin configuration (Added)
    CWR_LINE = 21;
    CWKEY_LINE = -1;
    PTTIN_LINE = -1;
    PTTOUT_LINE = -1;
    CWOUT_LINE = -1;
    t_print(" radioberry2 selected \n");
    /*
    CWL_LINE = 5;   <-- The default GPIO pin configuration has been commented out.
    CWR_LINE = 6;
    CWKEY_LINE = 12;
    PTTIN_LINE = 16;
    PTTOUT_LINE = 22;
    CWOUT_LINE = 23;
    */
       :

Notes:  
 pihpsdr recognise radioberry as follows
  pihpsdr/src/radio.c
    void radio_start_radio() {

      if (device == DEVICE_HERMES_LITE2) {
        if (realpath("/dev/radioberry", NULL) != NULL) {
          //
          // This is a RadioBerry.
          //
          if (radio->software_version < 732) {
            have_radioberry1 = 1;
          } else {
            have_radioberry2 = 1;
          }
        }
      }


Pihpsdr_LOG:
 After  change:
     1.052 gpio_set_defaults: Controller=0
     1.052  radioberry2 selected
     1.052 *** have_radioberry1 = 0
     1.052 *** have_radioberry2 = 0   <-- GW=73.2 and above:'1' (NG)
     1.052 *** CWL_LINE = 17   <-- Force pin configuration (OK)
     1.052 *** CWR_LINE = 21   <-- Force pin configuration (OK)
     1.127 discovery: showing device dialog
     1.128 discovery: devices=2 autostart=0
    42.800  *** have_radioberry2 ***
    42.801 gpio_init: GPIO device=/dev/gpiochip4

 Before change:
     1.037 gpio_set_defaults: Controller=0
     1.037 *** have_radioberry1 = 0
     1.037 *** have_radioberry2 = 0   <-- GW=73.2 and above:'1' (NG)
     1.037 *** CWL_LINE = 5   <-- Default GPIO pins are being used (NG)
     1.037 *** CWR_LINE = 6   <-- Default GPIO pins are being used (NG)
     1.113 discovery: showing device dialog
     1.113 discovery: devices=2 autostart=0
     6.254  *** have_radioberry2 ***   <--   No display "radioberry2 selected" (NG)
     6.254 gpio_init: GPIO device=/dev/gpiochip4
//

p.s.  Also checked that the pihpsdr cw-keyer is working. (modified mogpio.c v2.6)
Yado-san, jg1twp

2025年10月31日金曜日 8:50:57 UTC+9 SNAIL:

Negativ Zero

unread,
Oct 31, 2025, 1:50:50 PM (4 days ago) Oct 31
to Jatteau Marc, Radioberry
Yes,working,GUI best then 2,5,but much unresolved issue(vox must wkd only on tx...now not,sidetone...no wkd...etc!
Best 73..9a3ru

--
You received this message because you are subscribed to the Google Groups "Radioberry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to radioberry+...@googlegroups.com.

Yado-san

unread,
Oct 31, 2025, 9:06:33 PM (4 days ago) Oct 31
to Radioberry
Thank you for informing, pihpsdr v2.6  working.
I have deleted my incorrect analysis posted last night to avoid trouble.
I will also try reinstalling it myself.
Yado-san, jg1twp

2025年11月1日土曜日 2:50:50 UTC+9 Negativ Zero:

SNAIL

unread,
Nov 1, 2025, 12:30:17 AM (4 days ago) Nov 1
to Radioberry
Hi all. Can someone please make it clear to me what pins numeration do we use in PIHPSDR files? Is it RPI 40 pin connector or CN301 on Radioberry hat? Or something else?
I have ver 2.6 installed with GPIO off, ALSA AUDIO, MIDI on newer OS. In CW mode, CW handled in radio OFF pin 14 on CN301 transmit nice dots with side tone. Pin 13 acting like MOX or PTT in SSB mode. 
Enabling local microphone in TX menu causing some noise increase. Just little bit.
Reply all
Reply to author
Forward
0 new messages