Jetson Orin Nano CAN Issues

Issue Overview

Users are experiencing difficulties with the CAN (Controller Area Network) functionality on the Nvidia Jetson Orin Nano Dev board, particularly when using Jetpack 6.0. The specific symptoms reported include:

• Inability to get CAN to function properly despite following setup instructions.
• Users are unsure how to verify the kernel Device Tree Blob (DTB) settings related to CAN.
• The issue arises during the setup phase, specifically when attempting to configure and test the internal mttcan (Multi-Threaded CAN) interface.

The hardware in question is the Nvidia Jetson Orin Nano, and users have mentioned using both devkits and custom boards. The problem appears to be consistent among multiple users, affecting their ability to utilize CAN for their applications, which significantly hampers functionality for projects requiring this communication protocol.

Possible Causes

Several potential causes for the CAN functionality issues on the Jetson Orin Nano have been identified:

• Hardware Incompatibilities or Defects: If the board or peripherals are not compatible or are defective, it could prevent proper operation of the CAN interface.

• Software Bugs or Conflicts: There may be bugs in Jetpack 6.0 that affect CAN functionality, or conflicts with other installed software components.

• Configuration Errors: Incorrect settings in the kernel Device Tree may lead to the mttcan nodes not being properly enabled or configured.

• Driver Issues: If the necessary drivers for CAN are not correctly installed or configured, it could result in non-functional CAN communication.

• Environmental Factors: Issues such as inadequate power supply or overheating could impact performance and lead to failures in communication.

• User Errors or Misconfigurations: Users may misconfigure settings without realizing it, leading to issues with CAN operation.

Troubleshooting Steps, Solutions & Fixes

To resolve the issues with CAN on the Jetson Orin Nano, follow these troubleshooting steps and solutions:

1. Check Kernel Device Tree Configuration:

   • Decompile the kernel DTB file located in /boot/ using a command like:

     dtc -I dtb -O dts -o output.dts /boot/kernel_XXX.dtb
     

   • Look for mttcan configurations in output.dts:

     mttcan@c310000 {
         status = "okay";
     };
     mttcan@c320000 {
         status = "okay";
     };
     

2. Verify Hardware Setup:

   • Confirm whether you are using a development kit or a custom board.
   • Ensure that all connections related to CAN are secure and correctly configured.

3. Internal Loopback Test:

   • Use internal loopback testing for mttcan by enabling loopback mode in your software configuration.
   • This can help isolate whether the issue is with hardware or software.

4. Update Software and Drivers:

   • Ensure that you are using the latest version of Jetpack and that all drivers are updated.
   • Check Nvidia’s documentation for any patches or updates related to CAN functionality.

5. Review Power Supply and Environmental Conditions:

   • Ensure that your power supply meets the requirements of the Jetson Orin Nano.
   • Monitor temperatures and ensure proper cooling to avoid thermal throttling.

6. Consult Documentation:

   • Refer to Nvidia’s official documentation on Controller Area Network (CAN) for additional configuration details:
     Nvidia Developer Guide

7. Seek Community Support:

   • Engage with forums and community discussions for shared experiences and solutions from other users facing similar issues.

8. Best Practices for Future Prevention:

   • Regularly check for software updates from Nvidia.
   • Maintain proper documentation of your configurations to quickly identify misconfigurations in future setups.

By following these steps, users should be able to diagnose and resolve their issues with CAN on the Jetson Orin Nano effectively. If problems persist after these troubleshooting efforts, further investigation into specific hardware components may be necessary.