November 18, 2022, 5:21am
Is the pin number and gpio correctly matched in the Xavier NX Pinmux Configuration Template excel file?
I have a question because the gpios of 104 and 106 seem to have changed.
I’m testing the motor, but it works in the opposite direction to the expected direction, so I’m asking if the value in the excel is correct.
may I know which JetPack release you’re using? had you also refer to developer guide for identify the GPIO numbers.
November 21, 2022, 4:31am
may I know which JetPack release you’re using?
=> R32 (release), REVISION: 7.1
had you also refer to developer guide for identify the GPIO numbers.
=> yes. I have refered to Jetson_Xavier_NX_Pinmux_Configuration_Template_v1.06.xlsm
according to GPIO allocation ranges and its formula.
$ dmesg | grep "registered GPIOs"
[ 0.989710] gpiochip_setup_dev: registered GPIOs 288 to 511 on device: gpiochip0 (tegra-gpio)
#define TEGRA194_MAIN_GPIO_PORT_Y 24
#define TEGRA194_MAIN_GPIO(port, offset) \
((TEGRA194_MAIN_GPIO_PORT_##port * 8) + offset)
you should able to controls these two pins via sysfs.
GPIO3_PY.00 = ((24 * 8) + 0) + 288 = 480
GPIO3_PY.02 = ((24 * 8) + 2) + 288 = 482
please enter the location of the GPIOs,
you should generate
gpio480 name with…
# echo 480 > /sys/class/gpio/export
after that, you’ll be able to enable the GPIO for controlling.
$ cd /sys/class/gpio/gpio480
$ echo out > direction && echo 1 > value
November 22, 2022, 4:14am
Yes. I also calcuate pin number using formula you have mentioned.
It resulted in following table.
SODIMM Pin No.
It is related to Motorized Lenz control.
Motorized lenz proceed the other direction that I expected.
Could you inspect the xnx’s pinmux table using motorized lenz?
Motorized lenz spec is like below.
I don’t see other user report issues related to pinmux spreadsheets.
you may review the schematic, thanks
December 14, 2022, 2:55am
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.