Streaming Issues Between Cam0 and Cam1 Port in 2-Lane Mode on Nvidia Jetson Orin Nano Dev Board

Issue Overview

Users are experiencing streaming issues on the Nvidia Jetson Orin Nano Developer Kit when attempting to use the Argus application with two camera sensors connected to cam0 and cam1 ports in a 2-lane mode configuration. Specifically, while users can successfully stream video from cam1 using a calculated pixel clock value, they encounter a black screen when trying to stream from cam0.

The issue arises during the streaming process with the Argus application, despite successful operation with the V4L2 (Video for Linux 2) interface. The pixel clock calculation provided by users is as follows:

$$
pixel_clk_hz = sensor\ output\ size \times frame\ rate = (4072 \times 3176) \times 12 = 155192064
$$

Users have reported that they are not receiving any logs in the dmesg output when attempting to stream from cam0, which adds to the difficulty in diagnosing the problem. The issue seems to be consistent across multiple attempts and significantly impacts user experience by preventing access to video data from cam0.

Possible Causes

• Hardware Incompatibilities or Defects: There may be physical connection issues or defects in the camera module or the Orin Nano board that affect streaming capabilities.

• Software Bugs or Conflicts: The Argus application may have bugs or conflicts that prevent it from properly interfacing with cam0.

• Configuration Errors: Incorrect settings in the sensor device tree or lane polarity configurations could lead to improper communication with cam0.

• Driver Issues: Outdated or incorrect drivers for the camera modules could hinder functionality, particularly with Argus.

• Environmental Factors: Power supply issues or overheating could affect performance, especially if multiple sensors are used simultaneously.

• User Errors or Misconfigurations: Users might misconfigure settings in the device tree or fail to enable necessary parameters.

Troubleshooting Steps, Solutions & Fixes

1. Verify Hardware Connections:

   • Ensure that all physical connections between the camera sensors and the Orin Nano board are secure and properly configured.

2. Check Device Tree Configuration:

   • Review the sensor device tree settings for both cameras, particularly focusing on lane polarity and ensure it is correctly set for both cam0 and cam1.
   • Example configuration snippet:

     tcp: tegra-camera-platform {
         compatible = "nvidia, tegra-camera-platform";
         ...
         modules {
             cam_module0: module0 {
                 ...
                 drivernode0 {
                     ...
                 };
             };
             cam_module1: module1 {
                 ...
                 drivernode0 {
                     ...
                 };
             };
         };
     };
     

3. Examine Argus Daemon Logs:

   • Run the Argus daemon in the foreground to capture detailed logs:

     sudo su 
     pkill nvargus-daemon
     nvargus-daemon 2>&1 | tee argus-output.log
     

   • Analyze these logs for any error messages or warnings related to cam0.

4. Test V4L2 Functionality:

   • Since V4L2 works for cam0, compare the configurations used for V4L2 with those set for Argus. This may highlight discrepancies that need addressing.

5. Adjust Pixel Clock Settings:

   • Experiment with different pixel clock values based on various calculation methods suggested in the developer guide to see if this resolves streaming issues on cam0.

6. Review Kernel Messages:

   • Check kernel failure messages when starting streaming with Argus using:

     dmesg | grep nvargus
     

   • Look for timeout errors or other relevant messages indicating communication problems.

7. Contact Camera Vendor:

   • If issues persist, reach out to the camera module vendor (e-con team) for support and guidance specific to their hardware.

8. Firmware and Driver Updates:

   • Ensure that all firmware and drivers are up-to-date. Check Nvidia’s official documentation for any updates related to camera support on the Orin Nano platform.

9. Best Practices for Future Prevention:

   • Regularly update software and firmware.
   • Maintain proper documentation of configurations and changes made during setup.
   • Test new hardware configurations in isolation before integrating into existing systems.

By following these steps, users should be able to diagnose and potentially resolve streaming issues between cam0 and cam1 on their Nvidia Jetson Orin Nano Developer Kit.