Using jetson-nano-gpio-example as a reference, I’ve gotten input being detected on the pins that are already mapped within the included gpionano.h header.
I need more inputs that what is mapped/defined in the gpionano.h file.
In another thread here, someone mentioned to run ‘sudo cat /sys/kernel/debug/tegra_pinctrl_reg’
I ran that, and the address range output is all in 0x7000… range, which is strange to me, since all of the addresses in gpionano.h are in the x60000… range. This conflict is confusing to me, why are these addresses different?
Here is a spreadsheet I made in an attempt to organize what I’ve found so far.
I request a #define (address) for each gpio pin that is on the developer boards J41 GPIO Expansion Header.
Edit 3: I’ve forked the repo. and added an additional example for a keyboard emulator. While testing this, I did notice something seems incorrect with the initialization of the gpio pins via the methods used by these examples.
If I simply run the switch example, or my keyboard_emu example, input is not detected at all until after I go into python and setup the pin using the following code:
import RPi.GPIO as GPIO
Would it be possible for someone to look over the example code and recommend changes to properly init the pins without having to do the python stuff first? (I’ll push changes to my forked repo so that other users in the future may benefit from this)