12-05-2024, 12:14 PM
(This post was last modified: 12-05-2024, 12:27 PM by chano22000.
Edit Reason: How to turn "Problem" into "Solved"
)
Hello again,
Thanks Tim for what you achieve with Moode and nevertheless your attention to my previous message. Audiophonics may have nice hardware but software maintenance is mainly a customer job which I did !
In Moode 9, Rpi.GPIO is implemented through lgpio which leads to subtle differences with the native version. (rpi-lgpio 0.6 Documentation). An accurate control of GPIO pin usage and ownership is now provided leading to a"GPIO busy" error in case of a potential conflict.
In my case, the error was due to one GPIO pin setuped twice (without being first released) even redundantly :
de facto setups GPIO 17 as an input and marks is as used (gpioinfo) which conflicts with a later GPIO.setup(17, GPIO.IN) in ther initialisation script.
Voilà !
Best regards,
Philippe
(Sorry not to know how to turn "Problem" into "Solved"
Thanks Tim for what you achieve with Moode and nevertheless your attention to my previous message. Audiophonics may have nice hardware but software maintenance is mainly a customer job which I did !
In Moode 9, Rpi.GPIO is implemented through lgpio which leads to subtle differences with the native version. (rpi-lgpio 0.6 Documentation). An accurate control of GPIO pin usage and ownership is now provided leading to a"GPIO busy" error in case of a potential conflict.
In my case, the error was due to one GPIO pin setuped twice (without being first released) even redundantly :
Code:
dtoverlay=gpio-shutdown,gpio_pin=17,active_low=0,gpio_pull=downde facto setups GPIO 17 as an input and marks is as used (gpioinfo) which conflicts with a later GPIO.setup(17, GPIO.IN) in ther initialisation script.
Voilà !
Best regards,
Philippe
(Sorry not to know how to turn "Problem" into "Solved"
