You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Raspberry Pi 5 has been a PITA for lots of GPIO users as the hardware has changed significantly and many if not most software packages driving GPIO stopped working. Before I sink a lot of time trying to get Servoblaster to work on a RB Pi 5, I thought I’d ask if somebody has done that before and what the results were.
The text was updated successfully, but these errors were encountered:
Given the lack of quick responses and (mostly) the time of last updates, may I ask if this project is still actively supported? Obviously, no answer is a perfectly acceptable answer too in this case.
BTW—for all of those landing here searching the interwebs trying to get Servoblaster to work on an RB Pi 5, I couldn’t get it to work on RB Pi 5 with a “Failed to map peripheral” error message (after installing libraspberrypi-dev and raspberrypi-kernel-headers and fixing the cast of pointer to int error in line 69 of mailbox.c).
I looked at the servod.c code and decided not to pursue it any further since register-bit-banging is definitely well-suited for getting everything out of a given hardware, but survives significant hardware changes (like the one to RB Pi 5) usually very poorly. And who knows what RB Pi 6 will bring…
Raspberry Pi 5 has been a PITA for lots of GPIO users as the hardware has changed significantly and many if not most software packages driving GPIO stopped working. Before I sink a lot of time trying to get Servoblaster to work on a RB Pi 5, I thought I’d ask if somebody has done that before and what the results were.
The text was updated successfully, but these errors were encountered: