Orin PINMUX conflicted with pin description in design

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
, , ,
1

In desgin guide:

image
image1301×173 25.6 KB

but in PINMUX configuation:

image

Which one is correct? or we need to change PINMUX configuration? It seems a very basic issue, becuase it is a key power on/off signal.

Thanks

Peter

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, I couldn’t find any information related to the Jetson AGX Orin design guide image 1301173 or the specific PINMUX configuration issue you’re referring to. The context provided seems to be related to the Jetson Orin NX and Jetson Orin Nano Series Product Design Guide, which includes information on various interfaces such as SPI, CAN, Fan, and MIPI CSI.

However, I can provide some general guidance on how to approach this issue. If you’re experiencing a discrepancy between the design guide image and the PINMUX configuration, it’s possible that there might be a version mismatch or a configuration error.

To resolve this issue, I recommend the following steps:

  1. Verify the version of the design guide and the PINMUX configuration to ensure they match.
  2. Check the PINMUX configuration documentation to see if there are any specific guidelines or recommendations for configuring the power on/off signal.
  3. Compare the design guide image with the actual PINMUX configuration to identify any discrepancies.
  4. If necessary, update the PINMUX configuration to match the design guide image or consult with the relevant documentation or support resources to determine the correct configuration.

If you could provide more context or clarify the specific issue you’re experiencing, I’d be happy to try and assist you further.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

In design guide, MODULE_SHDN_N is output, but in PINMUX, it is input, which one is correct?

5

Any respnse? I think it’s the core signal initiated with Linux poweroff command.

7

Design Guide is Correct. Please update the Pinmux and update direction to Output.

9

Sgursal,

I chnaged the pinmux and rebuild the dtb, and found the module_shdn_n still couldn’t be low after we executed poweroff commnad in linux.

Peter

10

MODULE_SHDN_N and VDDIN_PWR_BAD_N do not play a role in user initiated software shutdown sequence.

11

Which signal play this role?

Peter

12

Software initiated shutdown is initiated through I2C bus to the power sequencer on the module.

13

Which signal is used for inform carrier board to turn off the module’s 12/5V supply after initiating by linux poweroff(software shutdown)? This commnad is frequently used by customer.

here is from desgin guide.

image
image1056×628 86.4 KB

image
image1023×639 81 KB

image
image1307×704 118 KB

i am quit confused about NV mentioned SW shutdown? other than poweroff commnad, is there anything else?

Peter

14

AGX Orin Design Guide is being updated to explain the different power down sequences and which signals are used in which scenarios. Expect to release soon.

15

Sgursal,

When can we get the update? By the way, this feature is very fundamental for a hardware with management ability, which should be implemented in inital version, not this stage.

Peter

16

the description in the red fram makes sense.

Peter

17

or SW shutdown is not correct. As mentioned earlier, MODULE_SHDN_N signal is not used in case of user initiated SW shutdown.

18

Sorry. The feature is implemented since beginning, however it is not documented correctly. Expect to be released soon. Can notify here once it is available for download.