Downloaded the pinmux spreadsheet and changed some settings and clicked DT… All that creates is a huge .dtsi that has an include that looks like it must be compiled in the kernel tree. I only need an overlay for some GPIO pins.
Hi foxsquirrel1,
Are you using the devkit or custom board?
What’s your Jetpack version in use?
May I know what’s your modification in pinmux? (i.e. what’s your use case?)
Jetpack 6.1
nvidia-l4t-core 36.4.0-20240912212859
Need 8 GPIO output lines, 2) i2c
Jetson orin nano devkit
Looking at the spreadsheet it does not identify the actual header pins on the nano board.
One of our products drives an 8 channel relay board and has a couple of i2c sensors. We have code using libgpiod with telemetry buried in it that is used to determine outliers on the gpio pins. Need to run that on your board for comparison to what we are using now.
Could you share the exact pin you want to use and its use case? (GPIO or I2C?)
Then I can instruct you for the configuration in pinmux spreadhseet.
40 pin Header pins:
i2c (3,5) (27,28)
GPIO outputs
7,15,29,31,33,32,16,18
If any of those GPIO selections will not mux just use 2 others that will.
Please refer to Generating the Pinmux dtsi Files to download and the steps to apply the change.
Let me take an example for I2C(PIN3, PIN5) and GPIO PIN7 of 40 pins expansion header.
Please check Expansion Header Pin Description – J12 in Jetson Orin Nano Developer Kit Carrier Board Specification.
For I2C1, you can configure it in pinmux spreadsheet as following:
For GPIO PIN7 of J12, you can configure it in pinmux spreadsheet as following:
You can refer to the above configuration for your another I2C interface(I2C0) and GPIOs(15,29,31,33,32,16,18)
1 Like
@KevinFFF Thank you very much for providing your assistance in getting our device tree configured.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.