So I am trying to figure out if I have a bad board, or if I’m missing something with some internal hardware that I’m not understanding how it works on the Nvidia Jetson NX
If I hook my multi-meter to pin 6 (ground) and pin 11, I see the voltage go from 0V to 3.3V as soon as I execute the final command from above, HOWEVER after about 5-8 seconds the the voltage will drop to roughly 1.5V and then from that point you can’t change the value (e.g. sending echo 0 > /sys/class/gpio/gpio428/value will do nothing it will stay 1.5V). If you send echo 0 ...echo 1 ... BEFORE it locks it changes voltage correctly.
Is there some other type of hardware in the newer NVidia Jetson Xavier NX units that cause this behavior? If so how would I fix it?
If I wait 5-8 seconds the gpio pin goes to 1.5v and you can’t change it. Any subsequent echo 1 > /sys/class/gpio/gpio428/value or echo 0 > /sys/class/gpio/gpio428/value and the pin stays at 1.5v.
I’ll get the Jetpack information as soon as I’m back in front of it tomorrow.
running the above, on the Xavier NX results in it going to 3.3V and then down to 1.5V after a short period of time. Only way to make it change values at that point is to disconnect the GPIO pin and then reconnect it and then it will drop down to 0V and then you can do it again.