Assistance with ‘RG10’ Pixel Format in Argus API for 360 Camera Application Using IMX477 and SyncStereo

Issue Overview

Users are encountering issues when trying to set the pixel format to ‘RG10’ (10-bit Bayer format) for the IMX477 sensor using the Argus API in a 360 camera application. The main symptoms include:

• Compilation Error: The constant PIXEL_FMT_RG10 is not recognized, resulting in a compilation failure when attempting to set the pixel format in the code.
• Initialization Failure: Users report that the cameras do not initialize properly, and error messages indicate that the camera isn’t being initialized correctly when using the SyncStereo feature.
• Context of Issue: The problem occurs during the setup phase of the application, specifically when configuring multiple IMX477 sensors for synchronized capture.
• Hardware Specifications: The IMX477 sensor supports resolutions of 3840×2160 at 30 fps and 1920×1080 at 60 fps, verified through the v4l2-ctl command.
• Frequency of Issue: This issue appears to be consistent among users attempting similar configurations.
• Impact: The inability to set the correct pixel format hinders the functionality of the SyncStereo feature, affecting the overall performance of the 360 camera system.

Possible Causes

Several potential causes have been identified for this issue:

• API Limitations: The current version of the Argus API may not support the RG10 pixel format, as indicated by user replies stating that only PIXEL_FMT_YCbCr_420_888 and PIXEL_FMT_RAW16 are recognized.
• Configuration Errors: Incorrect configuration or initialization code may lead to failures when attempting to set unsupported pixel formats.
• Driver Issues: If drivers are outdated or incompatible with the current software setup, they may prevent proper recognition of certain pixel formats.
• Software Bugs: There could be bugs within the Argus API that prevent it from recognizing or handling specific pixel formats correctly.

Troubleshooting Steps, Solutions & Fixes

To resolve this issue, users can follow these troubleshooting steps:

1. Verify Supported Formats:

   • Use the command:

     v4l2-ctl --list-formats-ext
     

     This command will list all supported pixel formats for the IMX477 sensor. Confirm whether RG10 is listed.

2. Check Argus API Documentation:

   • Consult the official Argus API documentation to verify which pixel formats are supported in your version. If RG10 is not mentioned, consider using an alternative format like PIXEL_FMT_RAW16.

3. Modify Code for Supported Formats:

   • If RG10 is unsupported, modify your code to use a recognized format:

     iEGLStreamSettings->setPixelFormat(PIXEL_FMT_RAW16);
     

   • Test if this change resolves compilation errors and allows for proper camera initialization.

4. Update Drivers and Software:

   • Ensure that all drivers related to your Jetson platform and IMX477 sensor are up-to-date. Check NVIDIA’s developer site for any available updates.

5. Testing Initialization Code:

   • Review and test initialization sequences for both single and multiple sensors. Ensure that each camera is properly initialized before attempting to synchronize them.

6. Check for Environmental Factors:

   • Ensure that power supply and temperature conditions are optimal for operation. Environmental factors can sometimes affect hardware performance.

7. Reach Out for Community Support:

   • If issues persist, consider reaching out on NVIDIA developer forums or other community platforms where similar problems have been discussed.

8. Documentation and Examples:

   • Refer to example codes provided in NVIDIA’s SDK or community forums that demonstrate successful implementations of similar setups.

9. Best Practices for Future Prevention:

   • Regularly check NVIDIA’s developer resources for updates on supported features and best practices when working with new hardware configurations.

By following these steps, users should be able to diagnose and potentially resolve issues related to setting the RG10 pixel format in their applications. If problems continue, further investigation into specific error messages or logs may be necessary to identify underlying issues.