Jetson Orin Nano & Flir Blackfly S Spinview Flickering

Issue Overview

Users are experiencing a flickering preview image when running the Spinview application on the Nvidia Jetson Orin Nano Developer Kit, specifically with the Flir Blackfly S camera connected via USB. The flickering occurs exclusively in continuous capture mode, although the camera continues to capture images correctly. This issue does not manifest when the same camera and cable are used with a different laptop, indicating that the problem is likely related to the Jetson Orin Nano setup or configuration.

Symptoms:

• Continuous flickering in Spinview during continuous capture mode.
• Normal image capture functionality, as images are still being picked up by the camera.

Context:

• The issue arises during the operation of Spinview with the Flir Blackfly S camera.
• The problem is isolated to the Jetson Orin Nano, as it does not occur on other hardware setups.

Frequency:

• The flickering issue appears consistently when using continuous capture mode on the Jetson Orin Nano.

Impact:

• The flickering significantly disrupts user experience and may hinder effective monitoring or analysis tasks that rely on stable image feeds.

Possible Causes

• Hardware Incompatibilities or Defects: There could be compatibility issues between the Jetson Orin Nano and the Flir Blackfly S camera, or potential defects in either device affecting performance.

• Software Bugs or Conflicts: Bugs within Spinview or conflicts with other installed software may lead to instability when processing video feeds.

• Configuration Errors: Incorrect settings within Spinview or system configurations could result in improper handling of data from the camera.

• Driver Issues: Outdated or incompatible drivers may cause communication problems between the Jetson Orin Nano and the Flir Blackfly S camera.

• Environmental Factors: External factors such as power supply inconsistencies could affect performance, especially under continuous load conditions.

• User Errors or Misconfigurations: Incorrect setup steps or parameters might lead to unexpected behavior during operation.

Troubleshooting Steps, Solutions & Fixes

1. Check Kernel Messages:

   • Use the command below to check for any error messages that might provide insight into the flickering issue:

     dmesg | grep -i error
     

2. Boost Clock Speeds:

   • Boosting clock speeds may help stabilize performance. Execute the following commands:

     sudo jetson_clocks
     sudo su
     echo 1 > /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
     cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate
     

3. Test with Different Applications:

   • Run alternative applications that utilize video capture to determine if the flickering is specific to Spinview.

4. Update Drivers and Firmware:

   • Ensure that all relevant drivers for both the Jetson Orin Nano and Flir Blackfly S camera are up to date. Check Nvidia’s official site for any firmware updates.

5. Isolate Hardware Issues:

   • If possible, test with another USB cable or port on the Jetson Orin Nano to rule out hardware connection issues.

6. Check Power Supply:

   • Verify that the power supply is adequate for both the Jetson Orin Nano and connected peripherals. Insufficient power can lead to performance issues.

7. Reconfigure Settings in Spinview:

   • Review and adjust settings within Spinview related to video capture and processing to ensure they are optimized for use with the Jetson Orin Nano.

8. Consult Documentation:

   • Refer to official documentation for both Nvidia Jetson and Flir Blackfly S for any specific configuration guidelines or troubleshooting tips.

9. Community Support:

   • Engage with community forums for additional insights or similar experiences from other users who may have resolved this issue.

Recommended Approach:
Users have reported success with boosting clock speeds as an effective workaround for stabilizing image feeds in Spinview. This should be prioritized when troubleshooting.

Unresolved Aspects:
Further investigation may be needed into specific software bugs within Spinview that could contribute to this issue, as well as potential compatibility updates from Nvidia regarding newer hardware integrations.