Capture image error

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

Hello, our camera is currently unable to produce images properly. The log is as follows. What is the cause of this issue

root@aa:~# cat /sys/kernel/debug/tracing/trace

tracer: nop

entries-in-buffer/entries-written: 9/9 #P:8

_-----=> irqs-off

/ _----=> need-resched

| / _—=> hardirq/softirq

|| / _–=> preempt-depth

||| / delay

TASK-PID CPU# |||| TIMESTAMP FUNCTION

| | | |||| | |

 kworker/3:2-131     [003] ....   274.523231: rtcpu_string: tstamp:9019458966 id:0x04010000 str:"VM0 deactivating."
 kworker/3:2-131     [003] ....   290.263208: rtcpu_string: tstamp:9511545949 id:0x04010000 str:"VM0 activating."
 kworker/3:2-131     [003] ....   290.715198: rtcpu_vinotify_event: tstamp:9525435721 cch:1 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:304812963104 data:0x759d580010000000
 kworker/3:2-131     [003] ....   290.715200: rtcpu_vinotify_event: tstamp:9525435875 cch:1 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:304813005792 data:0x0000000031000001
 kworker/3:2-131     [003] ....   290.831205: rtcpu_vinotify_event: tstamp:9528691316 cch:1 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:304911719648 data:0x759d550010000000
 kworker/3:2-131     [003] ....   290.831207: rtcpu_vinotify_event: tstamp:9528691461 cch:1 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:304911763008 data:0x0000000031000002
 kworker/3:2-131     [003] ....   300.083223: rtcpu_isp_falcon_task_start: tstamp:1227330936 ch:0 task:HANDLE_EVENT
 kworker/3:2-131     [003] ....   300.083228: rtcpu_isp_falcon_task_end: tstamp:1227330977 task:HANDLE_EVENT
 kworker/3:1-130     [003] ....   306.275250: rtcpu_string: tstamp:10012209536 id:0x04010000 str:"VM0 deactivating."
2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, I’ll try to help you identify the cause of the issue with your camera not producing images properly on the Jetson Orin NX platform.

Firstly, I’d like to note that the log you provided doesn’t seem to be directly related to the camera issue, as it appears to be a system log showing various kernel events. However, I’ll try to connect the dots using the information from the context.

From the context, I found a few potential issues that might be related to your problem:

  1. IMX219 camera issue: There’s a known issue (4385287) where the preview and capture with argus_samples and argus_camera fail when only one IMX219 camera is connected to the Jetson Orin NX 16GB/8GB, and a dual IMX219 overlay is applied. Although this issue is specific to the 16GB/8GB model, it’s possible that a similar issue might be occurring on your platform.
  2. Sensor-id issue: Another issue (4327644) mentions that when an IMX219 or IMX477 camera is connected to the Jetson Orin NX or Jetson Orin Nano devices through the CAM0 interface, users need to explicitly specify sensor-id=1 instead of the default sensor-id=0 in the gstreamer nvarguscamera element to correctly complete a camera recording. This might be related to your issue if you’re using a similar camera setup.
  3. IMX477 camera issue: There’s a known issue (4389380) where a half-preview image of IMX477 is observed when running argus_camera on the Orin Nano 4GB SKU4. Although this issue is specific to the Orin Nano, it’s possible that a similar issue might be occurring on your Jetson Orin NX platform.

To further troubleshoot the issue, I’d recommend checking the following:

  • Verify that your camera is properly connected to the Jetson Orin NX platform and that the CAM0 interface is being used.
  • Check your gstreamer pipeline to ensure that the sensor-id is correctly set to 1 (if applicable).
  • Try using a different camera module or a different platform to isolate the issue.
  • Review the system logs to see if there are any other error messages related to the camera or argus_camera tool.

If none of these suggestions help, please provide more information about your camera setup, the argus_camera tool version, and any other relevant details to help further diagnose the issue.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

The trace log shows didn’t receive any validate frame data from the MIPI bus. May need to probe the sensor output signal.

5

how to probe，thk！

6

Probe by scope.

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.