Orin Nano CAN Messaging Issue: Limited Transmission

Issue Overview

Users of the Nvidia Jetson Orin Nano Dev board have reported an issue where the device can only send two CAN (Controller Area Network) messages before ceasing transmission. This problem occurs while using the J17 pins in conjunction with a Waveshare CAN board.

Symptoms:

• The device successfully sends the first two CAN messages, which can be verified using candump.
• After sending these messages, the device stops transmitting further messages as if the CAN port has become disconnected.
• Incoming CAN messages can still be monitored using candump, indicating that the receive functionality remains operational.

Context:

• The issue arises during attempts to send CAN messages while connected to another device that continuously sends CAN messages.
• Users have noted that the problem persists despite the CAN interface appearing active when checked with ip link show.

Frequency:

• This issue has been consistently reported by users attempting similar setups.

Impact:

• The inability to send more than two messages significantly hampers communication in applications relying on CAN messaging, affecting overall functionality and user experience.

Possible Causes

• Hardware Incompatibilities or Defects: There may be issues with the Waveshare CAN board or connection to the Orin Nano that limit message transmission.

• Software Bugs or Conflicts: There could be bugs within the software stack managing the CAN interface that prevent proper message handling after initial transmissions.

• Configuration Errors: Incorrect settings in the CAN configuration may lead to unexpected behavior after a few successful transmissions.

• Driver Issues: Outdated or incompatible drivers for the CAN interface might cause communication failures after a limited number of messages.

• Environmental Factors: Power supply issues or temperature fluctuations could affect hardware performance, leading to intermittent failures.

• User Errors or Misconfigurations: Incorrect wiring or setup could result in limited functionality, even if initial tests appear successful.

Troubleshooting Steps, Solutions & Fixes

1. Initial Diagnosis:

   • Verify connections between the Orin Nano and the Waveshare CAN board.
   • Use ip link show to confirm that the CAN interface is up and running.

2. Check Software Configuration:

   • Ensure that the CAN interface is properly configured. Review settings and parameters relevant to your specific use case.

3. Monitor Logs:

   • Check system logs for any error messages related to CAN communication. Use commands like dmesg to gather insights.

4. Restart Devices:

   • As one user found success by restarting both the Orin Nano and the secondary device, this should be attempted as a first step in troubleshooting.

5. Test with Different Hardware:

   • If possible, test with another Waveshare CAN board or different wiring configurations to rule out hardware defects.

6. Update Drivers and Firmware:

   • Ensure that all drivers related to the CAN interface are up-to-date. Check for any available firmware updates for both the Orin Nano and the Waveshare board.

7. Isolate Environmental Factors:

   • Confirm that power supply levels are stable and within specifications for both devices.
   • Monitor operating temperatures to ensure they are within safe limits during operation.

8. Consult Documentation:

   • Review relevant documentation for both the Orin Nano and Waveshare CAN board for any specific configuration guidelines or known issues.

9. Best Practices for Future Prevention:

   • Maintain updated software and firmware versions.
   • Regularly check connections and configurations before starting projects involving CAN messaging.

Unresolved Aspects

While restarting devices resolved the issue for one user, it remains unclear why this specific limitation occurs after only two messages are sent. Further investigation may be needed to identify underlying software bugs or hardware limitations contributing to this behavior.