-
-
Notifications
You must be signed in to change notification settings - Fork 762
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
GPIO driver implementation does not use conform to BCM2711 (RPi4) #81
Comments
OMG, a brand new and shiny I wasn't aware this was released recently. Nor was I aware that there are significant differences between the Pi3/Pi4 GPIO to be honest, because on my Pi4 it just worked out-of-the box, so I never questioned this. While I cannot dive deep into your findings right now, all of this sounds plausible. I guess it makes sense split |
I'll test it on my side and then add it to the tutorials asap! |
I would argue that since the USB-serial is already connected when the Pi executes the GPIO init code, It might still make sense to configure pull-up resistors for the pins. They would ensure the pin always falls back to the default value Best, |
Thank you |
According to https://github.com/RPi-Distro/raspi-gpio/blob/master/raspi-gpio.c#L194 and to BC2711 ARM Peripherals, there is no more a
GPPUD0
register. InsteadGPPUPPDN0
is the register to use. Additionally, the procedure for pull-up/pull-down activation does not use theGPPUDCLK0
for BCM2711.Could this be behind some of the glitches we randomly see when using the chainloader?
I have made changes as per the below diffs and tested several times on Pi 4 with no issues when plugging/unplugging the USB serial cable. I am not sure though if I should enable pup/pdn for the TX or RX when using a serial to USB cable. Maybe you could enlighten me there.
The text was updated successfully, but these errors were encountered: