In desgin guide:
but in PINMUX configuation:
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
*** 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:
- Verify the version of the design guide and the PINMUX configuration to ensure they match.
- Check the PINMUX configuration documentation to see if there are any specific guidelines or recommendations for configuring the power on/off signal.
- Compare the design guide image with the actual PINMUX configuration to identify any discrepancies.
- 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. ***
In design guide, MODULE_SHDN_N is output, but in PINMUX, it is input, which one is correct?
Any respnse? I think it’s the core signal initiated with Linux poweroff command.
Design Guide is Correct. Please update the Pinmux and update direction to Output.
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
MODULE_SHDN_N and VDDIN_PWR_BAD_N do not play a role in user initiated software shutdown sequence.
Which signal play this role?
Peter
Software initiated shutdown is initiated through I2C bus to the power sequencer on the module.
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.
i am quit confused about NV mentioned SW shutdown? other than poweroff commnad, is there anything else?
Peter
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.
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
the description in the red fram makes sense.
Peter
or SW shutdown is not correct. As mentioned earlier, MODULE_SHDN_N signal is not used in case of user initiated SW shutdown.
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.
If this feature exists, the only possible siganls would be MODULE_SHDN_N and MODULE_SLEEEP_N, because there is no other similar signals.
If you has known the answer, could you let me know the answer? I can try quickly, becuase we have a onboad MCU to control these management signals.
Peter
I tried to trigger by CARRIER_POWER_ON, it worked with poweroff commnad. If this is the conclusion, then too many wrong infomation in design guide. This was not supposed to happened, not to mention NVIDIA, and a product with so many years.
Peter
Did check internally. Both seem to be correct. MODULE_SHDN_N is Output from the Jetson Module perspective going towards the Carrier Board and hence is described as Output in the DG.
MODULE_SHDN_N is also connected internally on the Jetson module to another signal through a resistor on the module which is configured as CMOS Output signal and hence MODULE_SHDN_N is Input in the pinmux as it reflects the view from Orin SOC perspective. This is to avoid output conflict with the other signal on the module.
CARRIER_POWER_ON signal should be used as the trigger to turn off 5V/12V “SYS_VIN_MV/HV”.
Correct? Does poweroff command trigger MODULE_SHDN_N?
Peter
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.