Nvidia Jetson Orin Nano Dev Board Camera Issue: No Image Output with MAX9295 + MAX9296 + IMX390

Issue Overview

Users are experiencing an issue with the Nvidia Jetson Orin Nano development board where they are unable to get image output when using the MAX9295 + MAX9296 + IMX390 camera setup. The problem occurs specifically with the Orin Nano module running JetPack R35.3.1, while the same configuration works correctly on a TX2 NX module with JetPack 4.5. The issue manifests as a timeout error in the capture process, with no sensor-related messages appearing in the VI tracing logs.

Possible Causes

1. SerDes Pixel Clock Configuration: The initial SerDes Pixel Clock setting may have been inappropriate for the Orin Nano, causing issues with data transmission.

2. Deskew Calibration: For high data-rate sensors (>1.5 Gbps), deskew calibration is necessary, which may not have been properly implemented in earlier JetPack versions for the Orin Nano.

3. Hardware Differences: There might be subtle differences in the camera interface implementation between the TX2 NX and Orin Nano modules, affecting compatibility with the same camera setup.

4. Software/Driver Incompatibility: The camera drivers or software stack on the Orin Nano with JetPack R35.3.1 might not be fully compatible with the MAX9295 + MAX9296 + IMX390 configuration.

5. Firmware Issues: There could be firmware-related problems specific to the Orin Nano that affect the camera interface.

Troubleshooting Steps, Solutions & Fixes

1. Adjust SerDes Pixel Clock:

   • Modify the SerDes Pixel Clock setting to 200,000,000.
   • Test image capture using the v4l-ctl command after this change.

2. Check Image Output:

   • If frames can be captured after adjusting the SerDes Pixel Clock, use a YUV tool to view the image.
   • If the image appears black, further investigation is needed.

3. Update to JetPack 5.1.2 or Later:

   • JetPack 5.1.2 includes a bug fix that adds deskew calibration support for high data-rate sensors.
   • Update the Orin Nano to this version or later to potentially resolve the issue.

4. Implement Deskew Calibration:

   • For data rates higher than 1.5 Gbps, ensure that deskew calibration is properly implemented.
   • Consult the Nvidia documentation for specific instructions on enabling and configuring deskew calibration for your setup.

5. Verify Camera Configuration:

   • Double-check that the MAX9296 is configured for 4-lane output.
   • Confirm that the image format is set to 1920×1080@30fps.

6. Analyze System Logs:

   • Review the dmesg log and trace.log for any error messages or anomalies.
   • Look for specific errors related to the camera interface, NVCSI, or VI (Video Input) subsystem.

7. Compare TX2 NX and Orin Nano Configurations:

   • Identify any differences in device tree overlays or camera-related configurations between the two platforms.
   • Adjust the Orin Nano configuration to match the working TX2 NX setup as closely as possible.

8. Contact Nvidia Support:

   • If the issue persists after trying the above steps, reach out to Nvidia developer support for further assistance.
   • Provide detailed logs, including dmesg output, trace logs, and any relevant configuration files.

9. Test with Different Camera Models:

   • If possible, test the Orin Nano with other compatible camera models to isolate whether the issue is specific to the MAX9295 + MAX9296 + IMX390 combination.

By following these troubleshooting steps and implementing the suggested fixes, users should be able to resolve the camera output issue on the Nvidia Jetson Orin Nano Dev Board. If problems persist, further investigation with Nvidia’s support team may be necessary to address any underlying hardware or software incompatibilities.