Re: sBitx Raspios Bookworm
|
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
>
|
