开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

sBitx Raspios Bookworm


 

With the release of Raspios Bookworm, Raspios Bullseye has become the legacy release and Buster is no longer available for download from the Raspberry Pi website.

Will sBitx run with newer versions of Raspios?
--
73,
Mark, N8ME


 

Bullseye is available on the Raspberry Pi website and Imager app:


 

You are correct Bullseye is now the legacy version. My question is how to get Buster (the previous legacy version). My understanding is that sBitx requires Buster.
--
73,
Mark, N8ME


 

Hi Mark,

I never run RaspiOS Buster in the sBitx. I have being always with Bullseye 64 bit - all good. Should be the same with bookworm... there is nothing "special" in the sBitx software which makes is tied to any Linux distribution or version. Just take care of doing the proper alsa aloop setup and use the correct config.txt boot options.

- Rafael PU2UIT

On 10/19/23 01:10, Mark Erbaugh wrote:
With the release of Raspios Bookworm, Raspios Bullseye has become the legacy release and Buster is no longer available for download from the Raspberry Pi website.

Will sBitx run with newer versions of Raspios?
--
73,
Mark, N8ME


 

That's good information. Somehow, I got the impression that sBitx required Buster. It may have been something to do with the fact that WiringPi has been removed from the Bullseye repositories.
--
73,
Mark, N8ME


 

You can just install it. I maintain a fork and packages of it for bullseye 64 bit.


Packages here:


But it compiles without problem if on different distro / version. Upstream also works:


- Rafael

On 10/20/23 14:10, Mark Erbaugh wrote:
That's good information. Somehow, I got the impression that sBitx required Buster. It may have been something to do with the fact that WiringPi has been removed from the Bullseye repositories.
--
73,
Mark, N8ME


 

Didn't Bookworm change the sound system?

Is alsa supported anymore?

73,
-- Dave, N8SBE

On 2023-10-20 07:15, Rafael Diniz wrote:
Hi Mark,
I never run RaspiOS Buster in the sBitx. I have being always with Bullseye 64 bit - all good. Should be the same with bookworm... there is nothing "special" in the sBitx software which makes is tied to any Linux distribution or version. Just take care of doing the proper alsa aloop setup and use the correct config.txt boot options.
- Rafael PU2UIT


 

Alsa is always there (it is the driver + userland support). Bookworm uses by default pipewire (on top of alsa), but you can just remove it if it causes trouble.

- Rafael

On 10/20/23 14:21, Dave New, N8SBE wrote:
Didn't Bookworm change the sound system?

Is alsa supported anymore?

73,
-- Dave, N8SBE

On 2023-10-20 07:15, Rafael Diniz wrote:
Hi Mark,

I never run RaspiOS Buster in the sBitx. I have being always with Bullseye 64 bit - all good. Should be the same with bookworm... there is nothing "special" in the sBitx software which makes is tied to any Linux distribution or version. Just take care of doing the proper alsa aloop setup and use the correct config.txt boot options.

- Rafael PU2UIT



 

Thanks.

You mentioned you maintain a fork of WiriingPi. I've heard that the reason Raspberry Pi dropped it from their repo's was because the original developer stopped work on the project. Do you know if the RPi people are coming out with an official way to manipulate GPIO pins from software? It seems odd that that feature is missing from the official operating systems.
--
73,
Mark, N8ME


 

On Sat, Oct 21, 2023 at 02:23 PM, Mark Erbaugh wrote:

official way to manipulate GPIO pins

I didn't find an official statement.

I did see an interview with Eben Upton and he mentioned libgpiod but I can't find a reference for that.

I did find the following which shows libgpiod and gpiozero working on Pi 5 and rpi.gpio is said to not work.

I did check to see what came installed on my Pi 5 with Bookworm and here's what I see:

$ apt list | grep gpio | grep installed

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libgpiod2/stable,now 1.6.3-1+b3 arm64 [installed,automatic]
liblgpio1/stable,now 0.2.2-1~rpt1 arm64 [installed,automatic]
libpigpio-dev/stable,now 1.79-1+rpt1 arm64 [installed,automatic]
libpigpio1/stable,now 1.79-1+rpt1 arm64 [installed,automatic]
libpigpiod-if-dev/stable,now 1.79-1+rpt1 arm64 [installed,automatic]
libpigpiod-if1/stable,now 1.79-1+rpt1 arm64 [installed,automatic]
libpigpiod-if2-1/stable,now 1.79-1+rpt1 arm64 [installed,automatic]
pigpio-tools/stable,now 1.79-1+rpt1 arm64 [installed,automatic]
pigpio/stable,now 1.79-1+rpt1 arm64 [installed]
pigpiod/stable,now 1.79-1+rpt1 arm64 [installed,automatic]
python3-gpiozero/stable,stable,now 2.0-1 all [installed]
python3-lgpio/stable,now 0.2.2-1~rpt1 arm64 [installed,automatic]
python3-libgpiod/stable,now 1.6.3-1+b3 arm64 [installed]
python3-pigpio/stable,stable,now 1.79-1+rpt1 all [installed]
python3-rpi.gpio/stable,now 0.7.1~a4-1+b4 arm64 [installed]
raspi-gpio/stable,now 0.20191001 arm64 [installed]
rpi.gpio-common/stable,now 0.7.1~a4-1+b4 arm64 [installed,automatic]

Note that 'installed' doesn't necessarily mean 'works on Pi 5'.

Note my Pi 5 is not installed in the sbitx chassis nor does it have the sbitx software on it at this point in time so I can't test the sbitx with it right now.

-- Regards, Dave, N1AI


 

I just got a Pi 5 yesterday. Currently I'm not planning on replacing the Pi 4 in my sBitx DE.

Off topic: have you tried booting your Pi 5 from an external USB drive?? I have a USB3 enclosure with an NvME SSD. You can use the Raspberry Pi Imager software to create a bootable USB drive. I tried booting my Pi 5 it and while it boots and runs fine, if I try and update the software, I get a "drive was removed without ejecting error" and have to do a hard shutdown.? The failure is repeatable. The same NvME drive works fine on my Pi 4's (one in the sBitx) and my Pi 400. To eliminate the possibility that the drive was drawing too much current, I connected it to a powered USB3 hub - same failure.? I'm trying to figure out if the problem is with the Pi 5 in general or if my board is defective while I can still return it.
--
73,
Mark, N8ME


 

On Thu, Nov 2, 2023 at 01:12 PM, Mark Erbaugh wrote:

have you tried booting your Pi 5 from an external USB drive?

Sorry, no, I have not.

I'm still working through getting my USB3 NVMe to run sbitx correctly with Pi 4 and the old Buster-based OS that came with sbitx.

I just figured out what it was doing wrong, will update the other thread, it was a permissions thing for /dev/gpiomem.

Next I want to use some of the advice I read here to get it to run on Bullseye in 64 bit mode then try Bookworm.

Basically I want to take things one step at a time, always having a fall-back that works so if I screw something up I can still use the radio.

-- Regards, Dave, N1AI


 

I'm trying to run sbitx on a Pi 5. I've compiled it with the working WiringPi library from Rhizomatica, but get an error on running:
gpio: Unable to open GPIO direction interface for pin 17: No such file or directory
wiringPiISR: unable to open /sys/class/gpio/gpio17/value: No such file or directory

Has anyone had this and fixed it?

ps - I tried the gpiod library, but that throws up lots of errors on compile because all is different.
?


 

ps - running 64 bit Bookworm.
Looking through the WiringPi code, I see that as stated by Rhizomatica, there is no support for the Pi 5, in terms of code which can print the device type, but I don't know what that means for gpio. Is the GPIO mapping entirely different in the 5??


 

Tony,

WiringPi does not - and most likely will never - support the Pi 5. Have you read the README [1]?

You need to port Farhan's sbitx code, which should be simple, can just follow my code, which I implemented using gpiod [2], [3].

Cheers and good luck!
Rafael

[1]
[2]
[3]

On 1/27/24 15:52, Tony Abbey wrote:

I'm trying to run sbitx on a Pi 5. I've compiled it with the working WiringPi library from Rhizomatica, but get an error on running:
gpio: Unable to open GPIO direction interface for pin 17: No such file or directory
wiringPiISR: unable to open /sys/class/gpio/gpio17/value: No such file or directory

Has anyone had this and fixed it?

ps - I tried the gpiod library, but that throws up lots of errors on compile because all is different.


 

Hi Rafael

Thanks for the advice on gpiod. Yes I did read the readme, but hoping it didn't matter! Looking on the Rpi forums, I see that people are programming the RP1 chip to get gpio.?
I'll have to look see how you have supported the delay function of wiringpi, as well.

Tony?


 

Hi Tony,

Just use usleep() (or any other C standard sleep function) instead of delay(). That is the easier part. Gpiolib does exactly which you mention and much more. If your purpose is re-write gpiolib and call it WiringPi... I think it is like reinventing the wheel. I'm using the Pi5 with the sBitx, and it is just great!

- Rafael

On 1/28/24 09:36, Tony Abbey wrote:
Hi Rafael

Thanks for the advice on gpiod. Yes I did read the readme, but hoping it didn't matter! Looking on the Rpi forums, I see that people are programming the RP1 chip to get gpio.
I'll have to look see how you have supported the delay function of wiringpi, as well.

Tony


 

The sbitx uses only pin read and write from gpio. Even those are very slow. The I2C is not critical. The RTC is read just once when the sbitx starts. The si5351 is written only when you change the frequency. At worst, the updates are 5 times a second when you give the tuning knob a full spin.?
We can kickout the entire wiringpi code and directly use the gpio dev subsystem.
- f

On Sun, Jan 28, 2024, 1:40 PM Rafael Diniz <rafael@...> wrote:
Hi Tony,

Just use usleep() (or any other C standard sleep function) instead of
delay(). That is the easier part. Gpiolib does exactly which you mention
and much more. If your purpose is re-write gpiolib and call it
WiringPi... I think it is like reinventing the wheel. I'm using the Pi5
with the sBitx, and it is just great!

- Rafael

On 1/28/24 09:36, Tony Abbey wrote:
> Hi Rafael
>
> Thanks for the advice on gpiod. Yes I did read the readme, but hoping
> it didn't matter! Looking on the Rpi forums, I see that people are
> programming the RP1 chip to get gpio.
> I'll have to look see how you have supported the delay function of
> wiringpi, as well.
>
> Tony
>