We are using Orin NX on our customized carrier board and noticing one USB 3.0 intermittent connectivity issue.
when we try to connect a SSD to USB port slowly( giving enough time for the power to get stabilize on the SSD - indicated by the LED blinking ) , then it is successfully detected and seen in the disk manager.
whereas, when we connect the SSD to USB 3.0 port at normal speed, it does not connect some times and some times it shows up in the disk manager and when we try to click on the mount, it throws some error as shown.
Please let us know what might be the root cause for this behaviour.
Note: We are using redriver IC on our customized carrier board.
Thanks,
Nagesh R
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, I’ll attempt to provide a comprehensive answer to the question.
The issue described is related to intermittent connectivity problems with a USB 3.0 port on a customized carrier board using the Jetson Orin NX module. The problem occurs when connecting a Solid-State Drive (SSD) to the USB 3.0 port, and it seems to be related to the speed of connection.
Possible Root Causes:
Power stabilization: The fact that the SSD is successfully detected when connected slowly, allowing enough time for power to stabilize, suggests that power-related issues might be the root cause. The SSD might require a certain amount of time to stabilize its power consumption, which could be affected by the speed of connection.
Signal integrity: The use of a redriver IC on the customized carrier board might be contributing to the issue. Redrivers are used to improve signal integrity, but they can also introduce new problems if not properly configured or if the signal quality is poor.
UPHY lane sharing: The Jetson Orin NX module shares UPHY lanes between PCIE, UFS, and XUSB. This sharing might lead to conflicts or signal degradation, especially if the UPHY lane mapping and compatibility are not properly verified between the custom carrier board and the P3767 reference design.
ESD sensitivity: The Jetson Orin NX module contains ESD-sensitive parts, and improper handling or connection of devices can cause damage. Although this is not directly related to the connectivity issue, it’s essential to ensure that proper anti-static and grounding techniques are used when working with the system.
Comparison with the provided context:
The provided context mentions that the Jetson AGX Orin series can support up to four enhanced SuperSpeed Universal Serial Bus (USB) ports, but not all ports can be used due to UPHY lane sharing. This information is relevant to the issue, as it highlights the importance of verifying UPHY lane mapping and compatibility between the custom carrier board and the reference design.
The context also describes the USB structure, including the nine pins and the connection of D+/D− signal pins to UTMI pads and SSTX/SSRX signal pins to UPHY. This information is useful for understanding the signal flow and potential sources of signal degradation or interference.
Recommendations:
Verify the UPHY lane mapping and compatibility between the custom carrier board and the P3767 reference design to ensure proper signal routing and sharing.
Check the power consumption and stabilization of the SSD and ensure that the customized carrier board can provide a stable power supply.
Investigate the signal integrity and quality on the USB 3.0 port, using tools such as oscilloscopes or signal analyzers, to identify potential issues.
Ensure that proper anti-static and grounding techniques are used when working with the system to prevent ESD damage.
By following these recommendations, you should be able to identify and address the root cause of the intermittent connectivity issue with the USB 3.0 port on your customized carrier board.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
As per our hardware engineer, this SSD is inserted to USB 3.0 port, after 5 minutes of power on so there is enough time for power stablilization it seems.
Please let us know other possible reasons for this behavior.
