What is the key rules to config the custom pinmux on default official pinmux (Jetson orin nano) to flash custom pinmux

Hi

Now i am editing my custom config on default (official pinmux from downlaoded on official website) to flash my custom pinmux on my custom board.

what are key rules is there to config based on pin direction?

for example:

uart TX - output (pin direction) - Drive 1 (init req state)

like this for all protocols and everything to use like in the init req state it has Drive 0,1 and Z, N/A, int PU, PD like that.

i want correct key rules to config my custom pinmux??

Hi thaseen,

Are you using the Jetson Nano or Orin Nano on custom carrier board?

The pin state for UART case should be fine as it will be controlled by UART driver.

Please also refer to Jetson AGX Series Module Pinmux Application Note for the detailed usage for pinmux.

No i am asking the key rules to config custom pinmux

This application note shows you how to use the pinmux spreadsheet.

For the custom pinmux, please confirm the pinmux configurations match the design of your custom carrier board.

I am not able to trace that file

What do you mean about “trace the file”?
What’s your current requirement and what do you want to configure?

Leave it the above question

i opened that file in windows

After changing the config i click the button it showing this ? this issue may coming from i changed the customer usage names aslo the LLM’s saying this one:

Fix Customer Usage to match xlsm function names (required for VBA macro)

is it correct>?

Question:

  1. After generated dtsi files i have to copy the pinmux and padvoltage into BCT file and gpio file into Bootloader file right!?
  2. After copied that dtsi file what is the step to flash custom pinmux only not full whole os ?
  3. After flash how to validate that pins are changed or config any dmsg is there to check ?

What “customer usage names” did you modify in pinmux spreadsheet?
The pinmux spreadsheet will check if there’s invalid configuration before generating the pinmux/gpio dtsi.
I would suggest you downloading the default pinmux spreadsheet and generate the device trees w/o any custom modification.

Correct.

Please flash QSPI only or just flash the whole board.

You can run sudo busybox devmem <register> to read if the PADCTL register you modified has updated..

Could you also answer this as Jetson Nano and Orin Nano have different flow to handle pinmux?

jetson orin nano

Okay, I have moved your topic to the correct category for Orin Nano.

Is this still an issue to support? Any result can be shared?

No, i comfig and flashed QSPI and verified the pins are config using pincontrol