Difference in Available Sensor Modes when using RPi Camera V.2 with Orin Nano and Nano 2/4 GB

Issue Overview

Users have reported discrepancies in the available sensor modes when using the RPi Camera V.2 across different Jetson Dev Kits, specifically between the Nano 2GB/4GB and Orin Nano. The primary symptom observed is the absence of a specific high frame rate mode (1280 x 720 at 120 fps) on the Orin Nano, which is available on the older Nano models. This issue occurs when invoking the command gst-launch-1.0 nvarguscamerasrc sensor-id=0 from a bash terminal.

Context

• Hardware: Users are utilizing RPi Camera V.2 with Jetson Nano 2GB, Nano 4GB, and Orin Nano Dev Kits.
• Software: The issue arises during the execution of GStreamer commands to access camera capabilities.
• Frequency: The problem appears consistently across multiple users who have tested the same setup.
• Impact: The missing sensor mode significantly hampers users’ ability to extend their projects from older Nano models to the Orin Nano, particularly for applications requiring higher frame rates.

Possible Causes

1. Driver Issues: The driver for the camera may not fully support all sensor modes on the Orin Nano compared to older models.

   • This could lead to certain modes being unavailable due to differences in hardware architecture or software implementation.

2. Configuration Errors: There may be configuration settings that need adjustment for the Orin Nano to recognize all available sensor modes.

   • Improper setup could prevent access to specific capabilities of the camera.

3. Software Bugs: Potential bugs in the GStreamer framework or related libraries could limit functionality on newer hardware.

   • These bugs might not have been present or identified in earlier versions used with older devices.

4. Environmental Factors: Power supply or thermal management issues could affect performance and availability of certain modes.

   • If the board is not receiving adequate power or cooling, it may limit operational capabilities.

5. User Errors: Misconfigurations during setup or command execution could lead to this issue.

   • Users may inadvertently miss steps that enable full functionality.

Troubleshooting Steps, Solutions & Fixes

1. Verify Driver Installation:

   • Ensure that you have the latest drivers installed for the RPi Camera V.2 compatible with your Jetson board.
   • Use the command:

     sudo apt-get update
     sudo apt-get upgrade
     

2. Check GStreamer Installation:

   • Confirm that GStreamer is correctly installed and configured:

     gst-inspect-1.0 --version
     

3. Test with Different Commands:

   • Try invoking different commands to see if other modes are accessible:

     gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! nvoverlaysink
     

4. Manual Configuration of Sensor Modes:

   • If possible, manually configure sensor modes by editing configuration files or using command-line options that specify desired settings.

5. Use Alternative Software Versions:

   • Consider testing with earlier versions of JetPack or GStreamer if compatibility issues are suspected.
   • Flash your board with Jetpack 5.x instead of 6.x if you encounter persistent issues.

6. Community Resources:

   • Reference community discussions and documentation for similar issues and resolutions:
     • Check NVIDIA forums for updates on driver support and bug fixes related to camera functionalities.

7. Report Issues to NVIDIA Support:

   • If none of the above steps resolve the issue, report it directly to NVIDIA support for further assistance and potential driver updates.

8. Preventive Measures:

   • Regularly check for updates on drivers and software packages.
   • Keep a backup of working configurations before making significant changes.

Recommended Approach

Multiple users have had success by reverting to earlier software versions or manually configuring settings through community-sourced solutions. Engaging actively with NVIDIA’s developer forums can also provide timely insights into ongoing issues and fixes as they develop.

Unresolved Aspects

The possibility of a firmware update from NVIDIA that re-enables missing sensor modes remains unaddressed in current discussions, indicating a potential area for further investigation by users needing this functionality.