No - pi4j bypasses the kernel and talks directly to the hardware.Is there a chance to prohibit pi4j doing this?
I don't understand what you are suggesting here.Or shall i overwrite my pin definition file, so that it do not know these pins are also input pins and bind them strictly to RXD3, TDX3 & RXD4, TXD4?
Any kind of dts file, either proper Device Tree or the legacy dt-blob file that some firmwares use, is used long before pi4j runs, and gives no protection against its settings being trashed.I saw soemthing with a .dts file were this can be changed. Is this correct?
The only sensible fix is to work out which bit of pi4j, its configuration, or the application, is requesting that GPIO4 is used as an input, and then stop it from doing so.
Statistics: Posted by PhilE — Thu Feb 29, 2024 1:18 pm