Documentation for Pinmux Excel

Hello,
we made a custom carrier board for Orin NX.
Though we are struggling a bit to correctly fill in the pinmux excel table.
For example we noticed by experiment that I2C does not work if its pins “req. initial state” is set to “Z”, but they do work if it is set to “N/A”.
From an electronical point of view this was quite surprising to us.

So, is there any comprehensive guide on how to correctly fill in the pinmux excel, that mentions such caveats?
(We know about Jetson AGX Orin Platform Adaptation and Bring-Up — Jetson Linux<br/>Developer Guide 34.1 documentation but this does not contain a lot of information)

Hi jonathan.schnitzler,

What’s your Jetpack version in use?

There’re many logics in pinmux spreadsheet to determine the valid/invalid case.
If you configure the pin as Output, it is invalid with req. initial state as Z.

Hi, we use JetPack 5.1.2.
We did not configure the I2C pins as Output. We configured them as Bidirectional.
With initial state Z the MB2 had issues with I2C. With initial state N/A the MB2 had no issues.

There’re many logics in pinmux spreadsheet to determine the valid/invalid case.

Is this logic documented anywhere? Otherwise how are we supposed find this out?

You could refer to how other bus configured.
For I2C interfaces, it seems configured as Bidirectional, N/A.

You can also refer to 8.4.1.7 PinMux in Jetson Orin Series SoC Technical Reference Manual for details.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.