keypunch416

I just updated initial entry and title for issue. For reasons unknown until now and for last two days the N2 link on link referenced in issue was sending one...

I decided to try to display GPIO values via cat commands as shown in . Even GPIO value that worked with gpioget failed: cat /sys/class/gpio/gpio477/value cat: /sys/class/gpio/gpio477/value: No such file...

I am sure the pins I want to access are not reserved. I did not mention in log I tried to read the Blue LED and Fan pins via gpioget...

I happened ny pure chance on very unrelated search to across this link (as happens often enough over years) that covers a few Odriod devices. The N2 specific GPIO definitions...

Some sort of related searching re /sys/class/gpio/gpiochip427 (seems to be the 40 pin header on N2) found this link that states: Since linux 4.8 the GPIO sysfs interface is deprecated....

LED and power GPIO show as "[used] when run gpioinfo as would, UARTs, I1C and SPI if enabled and not is any were not enabled. gpioinfo fron the N2+: gpiochip0...

You may not be aware, but WiringPi is basically wrapper to sysfs. Ego same issue if one tries to use CLI to sysfs WRT N2 and other SBCs with alternate...

As I mentioned GPIO has worked so much better than sysfs and really all one is doing is instead of using a cli command to sysfs one is using a...

Various combinations of GPIO input pins tried to change state of return 0 as successful but in fact do not change GPIO state. For example (of various input GPIO pins...

Some Additional Testing: Manjaro-ARM same issues with gpioset and gpioget as DietPi 8.6.1. Official Hardkernel 22.04 same issues with gpioset and gpioget as DietPi 8.6.1, but gpio inverted meaning what...