I was going through GPIO python libraries and came across Jetson GPIO. If I am using a custom carrier, i.e. not the NVIDIA Developer Kit, can I still utilize this library?
Going through the README, I came across this statement, which I was particularly interested inGPIO.TEGRA_SOC mode.
GPIO.setmode(GPIO.BOARD)
# or
GPIO.setmode(GPIO.BCM)
# or
GPIO.setmode(GPIO.CVM)
# or
GPIO.setmode(GPIO.TEGRA_SOC)
With this mode set you provide a string that corresponds to the GPIO you’re trying to configure as output or input, but what would that look like? If I run: sudo cat /sys/kernel/debug/gpio
Would either of the highlighted options work (in the scenario they’re configured as a regular GPIO in the pinmux). Would I be able to define the pin HIGH/LOW by using either “gpio-487” or “PAC.01” as a parameter.
We wouldn’t think of a reason for the GPIO library not to work with your custom carrier.
Just take into consideration the difference that there might be between your carrier board’s pinmux and the devkit carrier board, since although the SOM will inherently have the same pins regardless of the carrier it is in, the routing on the carrier will probably change.
best regards,
Andrew
Embedded Software Engineer at ProventusNova
What do the integers 92, 41, 28 represent? Additionally, How do I get the signal name i.e. ‘CAM0_MCLK’
and ‘GP52_CLK1’, I am assuming those are capabilities of the PP.00 pin, depending on the pinmux, but where can I grab the corresponding signal name?