New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raspberry Pi 4B support #131
Comments
However, it would add to the pre-reqs to get the RPi include file. |
Hi Paul, the RapsberryPI connection type is deprecated. The future proof way is to use the gpio connection type instead. Incidentally there is a open pull request #119 to improve the gpio connection type that needs testing. Since I guess you are using lcdproc on a RPi: Could you test this PR for us? |
I don’t have access to RPi4 with nearby lcd until September ... but I saw someone asking questions about getting this working on RPi forum so I will highlight this over there. |
@PaulWebster Thanks for the links, this was very usefull. |
Bonjour, j'ai essayé votre driver pour Pi 4, et j'ai ce message d'erreur Driver [hd44780] init failed, return code -1 avez-vous une idée du problème? Merci. Jean |
Hello, I tried your driver pour Pi 4, and I got this error message : Driver [hd44780] init failed, return code -1 do you have an idea? Thank you. Jean |
@jduffas Sorry, not enought info to help you. But my driver is probably too old. I recompiled it with latest version of everything :) Unfortunatly, I'm not using it anymore (I switched to i2c), so I can't test it. |
Hello,
I did it working with original driver,
I had to select « gpio » instead of raspberry (I think)
Thank you :-)
Jean
Envoyé de mon iPhone
… Le 25 mai 2020 à 15:41, Cédric M. ***@***.***> a écrit :
@jduffas Sorry, not enought info to help you. But my driver is probably too old. I recompiled it with latest version of everything :) Unfortunatly, I'm not using it anymore (I switched to i2c), so I can't test it.
hd44780.so.zip
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I just tested #119 and left some comments. After changing a couple of #ifdefs, I did get that to work. I can definitely confirm that the raspberrypi connection does not find the right GPIO base for a Pi 4B (or a Pi 400) |
The Raspberry Pi 4B model has a different peripherals address.
Rather than hard-coding the value it would probably be better (and hopefully more future proof) to use the official RPi library to determine the base at run-time.
There is an issue with this though ... the RPi folks have not yet released an update to make it work but it is on their list to do.
See https://www.raspberrypi.org/documentation/hardware/raspberrypi/peripheral_addresses.md for the official way to do it and
https://www.raspberrypi.org/forums/viewtopic.php?f=33&t=244031&sid=9ae061e82d029dcf862ed051293d18cc#p1491303 for
RPi forum post about it
The text was updated successfully, but these errors were encountered: