Power Issues and I2C Transfer Timeouts on Jetson AGX Orin Developer Kit 64GB

, ,

Hello NVIDIA Community,

We are encountering significant power-related issues with our NVIDIA Jetson AGX Orin Developer Kit 64GB during robot testing. Below are the detailed observations and logs we’ve gathered to help diagnose the problem.


Hardware Details:

  • Device: Jetson AGX Orin Developer Kit 64GB
  • Backup Device: Another Jetson AGX Orin Developer Kit (Functioning Properly)

Issue Description:

While testing our robot, the primary Jetson AGX Orin suddenly shut down. Subsequent attempts to restart it have resulted in unreliable behavior. Initially, we powered the device using the jack port but faced the following issues:

  1. USB-C Power Supply:

    • Behavior: Pressing the power button causes the LED to turn on briefly and then go off.
    • Current Draw: Not measurable as the device fails to stay powered.
  2. Jack Port Power Supply:

    • Behavior: The device only powers on reliably when supplied with exactly 12V.
    • Current Draw:
      • New (Functional) Orin: Approximately 2.8A to 9A in idle.
      • Faulty Orin: Approximately 3.2A in idle, reducing to 0.9A post-boot.

    Despite the faulty Orin drawing lower current after booting, it remains significantly higher compared to the new device, and the device shuts down randomly, especially under high current draw.


Debug Serial Log Findings:

We connected to the faulty Jetson AGX Orin via a debug serial connection and obtained the following log snippets:

tegra-i2c c240000.i2c: I2C transfer timed out
ina3221 1-0040: Unable to reset device
ina3221: probe of 1-0040 failed with error -110

tegra-i2c c240000.i2c: I2C transfer timed out
ina3221 1-0041: Unable to reset device
ina3221: probe of 1-0041 failed with error -110

ucsi_ccg 1-0008: i2c_transfer failed -110
ucsi_ccg 1-0008: ucsi_ccg_init failed with error -110
ucsi_ccg: probe of 1-0008 failed with error -110

Concerns & Questions:

  1. I2C Transfer Timeouts and Device Probe Failures:

    • Devices Affected: INA3221 Power Monitors and UCSI CCG (USB Type-C Controller).
    • Error Code -110: Indicates a timeout (ETIMEDOUT), suggesting communication failures on the I2C bus.
  2. Impact on Power Functionality:

    • INA3221 Failures: These power monitors are essential for accurate voltage and current measurements, ensuring stable power delivery. Failures here could lead to unreliable power management.
    • UCSI CCG Failures: This controller manages USB Type-C power delivery. Its inability to initialize likely explains why the device cannot be powered via USB-C and faces issues with the jack port.
  3. Current Draw Anomalies:

    • The faulty Orin draws higher current at idle compared to the new unit and fails to maintain stable operation, especially under high load.

Troubleshooting Steps Taken:

  1. Power Supply Verification:

    • Confirmed that the power supply is stable and meets the required specifications.
  2. Port Testing:

    • Tested both USB-C and jack ports with various voltages. Only 12V via the jack port allows the device to power on, albeit unreliably.
  3. Current Measurement:

    • Compared the current draw of the faulty Orin with a new, functioning unit.
  4. Serial Log Analysis:

    • Connected via debug serial to capture and analyze log messages indicating I2C transfer timeouts and device probe failures.

Request for Assistance:

Given the above observations and log excerpts, we seek guidance on the following:

  1. Interpretation of I2C Errors:

    • Do the I2C transfer timeouts and probe failures for INA3221 and UCSI CCG indicate a hardware malfunction affecting power detection and management?
  2. Potential Solutions:

    • Hardware Inspection: Should we inspect or replace specific components related to the I2C bus or the affected devices?
    • Firmware/Software Configuration: Are there known firmware issues or device tree configurations that might resolve these I2C communication problems?
    • Alternative Diagnostics: What other diagnostic steps can we take to pinpoint and rectify the power instability?
  3. Preventive Measures:

    • Recommendations to prevent such issues in future deployments or during intensive testing phases.

Additional Information:

  • Operating Conditions: The device was running in a robotic application environment, which may involve variable power demands and mechanical stresses.
  • Recent Changes: No significant hardware or software changes were made prior to the sudden shutdown.

Thank you in advance for your support and expertise. We look forward to your guidance to resolve these issues and restore reliable operation to our Jetson AGX Orin Developer Kit.


Best Regards,

Orkun Acar
orkun-acar@outlook.com
OzU Rover


Attachments:

orin_log.pdf (452.8 KB)
( Sorry for uploading log as pdf :( permission issues)


Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!

Hello,

I got the log from jetson device attached the file in first post. Can you explain a little more about to comparing with host PC and jetson device?

I will try to re-flash it if i can manage to power up for few seconds. In case if i can not manage it can we still flash it without power?

Thanks. Waiting for your reply.

Kind regards

So i tried some few things more.

Here is a list:

  • It is turning off after 12V or close to 12V and above.
  • I flashed it again to check if issue persist and yes now i have more problems.
  • While trying to flash it failed twice after it can not detect USB. ( Flashed after so i didnt get the logs for it )

Now it can no longer detect devices that connected through USB port. So i am now unable to login or control orin through display.

I forgot to give some information about setup. AGX Orin Dev Kit 64 Gb i am using and i have x86 host pc that runs 22.04 ubuntu currently. I flashed the jetpack latest version which is jetpack 6.1. Also the keyboard input is working before boot. I can get in setup or boot configuration but i am not able to type anything after the boot. So i suspect a driver is missing in linux or something i dont know.

If any ideas come up i would like to hear them.

Do you have any suggestions so i can manage it to work?

Thanks.

Hi, it seems that your devkit has hardware issue, such as power monitor since it can not be reached. Devkit is for development in room only. It should not be used for product and in extreme environments. You may need to check and avoid too high temperature usage and extreme vibration during operation.

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