Unable to stream CSI camera video under the new Jetpack 6.2

Hi,

Environment: Jetson Orin NX 8GB + JNX42 Customized board + 2 X IMX715 sensors under CAM0 and CAM1, both in 4-lane bandwidth; JetPack 6.2

I’m using a customized carrier board with my Jetson Orin NX SoM. I updated the JetPack to 6.2, and also adjusted the sensor driver src codes which support JetPack 6.1 to adjust the new JetPack version. The two sensors can be detected under the v4l2-ctl --list-devices, but unable to stream the live video. When I run “nvgstcapture-1.0”, it showed me this error for all of the available modes and sensors:

nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadExecute:734 NvBufSurfaceFromFd Failed.
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadFunction:245 (propagating)

I attached the sensor dts files below, it would be great if someone can give any suggestion if I miss anything. Thanks!

Best,
Wenhai.
tegra234-p3767-camera-p3768-fr_imx715-cam0-4lane-overlay.txt (8.9 KB)

tegra234-p3767-camera-p3768-fr_imx715-cam1-4lane-overlay.txt (8.9 KB)

tegra234-p3767-camera-p3768-fr_fpa_a_p22-overlay.txt (8.9 KB)

hello calvin0328,

could you please refer to developer guide, Applications Using V4L2 IOCTL Directly to use V4L2 IOCTL to verify basic camera functionality.
for instance,
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100

Hi Jerry,

I have verified through running the following commands, the outputs are as expected, sensor functioning well. The issue is only happening when streaming with Jetson ISP through argus.

Output:

v4l2-ctl -d /dev/video0 --set-fmt-video=width=3864,height=2192,pixelformat=GB10 --set-ctrl frame_rate=60000000 --set-ctrl bypass_mode=0 --stream-mmap
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.00 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.00 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.00 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.00 fps
v4l2-ctl -d /dev/video1 --set-fmt-video=width=3864,height=2192,pixelformat=GB10 --set-ctrl frame_rate=60000000 --set-ctrl bypass_mode=0 --stream-mmap
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.02 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.02 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.02 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.02 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.02 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.02 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.02 fps

Also I have checked that the dumped raw bayer data via v4l2 is correct.

hello calvin0328,

thanks for testing, it looks basic camera functionality works normally.
let’s further test with gst pipeline to disable preview and shows frame-rate only,
for instance,
$ gst-launch-1.0 nvarguscamerasrc sensor-id=0 sensor-mode=0 ! 'video/x-raw(memory:NVMM),width=1920, height=1080, framerate=30/1, format=NV12' ! nvvidconv ! fpsdisplaysink text-overlay=0 name=sink_0 video-sink=fakesink sync=0 -v

Hi Jerry,

Thanks for the further help, I just tested but I got the same error msg that I had seen after run “nvgstcapture-1.0”:

gst-launch-1.0 nvarguscamerasrc sensor-id=0 sensor-mode=0 ! 'video/x-raw(memory:NVMM),width=3864, height=2192, framerate=60/1, format=NV12' ! nvvidconv ! fpsdisplaysink text-overlay=0 name=sink_0 video-sink=fakesink sync=0 -v
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0/GstFakeSink:fakesink0: sync = false
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
/GstPipeline:pipeline0/GstNvArgusCameraSrc:nvarguscamerasrc0.GstPad:src: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:src: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/Gstnvvconv:nvvconv0.GstPad:src: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0.GstGhostPad:sink.GstProxyPad:proxypad0: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0/GstFakeSink:fakesink0.GstPad:sink: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0.GstGhostPad:sink: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/Gstnvvconv:nvvconv0.GstPad:sink: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:sink: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
GST_ARGUS: Creating output stream
CONSUMER: Waiting until producer is connected...
GST_ARGUS: Available Sensor modes :
GST_ARGUS: 3864 x 2192 FR = 90.000001 fps Duration = 11111111 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 22000, max 660000000;

GST_ARGUS: 1296 x 720 FR = 260.000057 fps Duration = 3846153 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 22000, max 660000000;

GST_ARGUS: 1920 x 1080 FR = 90.000001 fps Duration = 11111111 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 22000, max 660000000;

GST_ARGUS: 3864 x 2192 FR = 59.999999 fps Duration = 16666667 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 32000, max 660000000;

GST_ARGUS: 1296 x 720 FR = 174.000013 fps Duration = 5747126 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 32000, max 660000000;

GST_ARGUS: Running with following settings:
   Camera index = 0
   Camera mode  = 0
   Output Stream W = 3864 H = 2192
   seconds to Run    = 0
   Frame Rate = 90.000001
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadExecute:734 NvBufSurfaceFromFd Failed.
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadFunction:245 (propagating)
Redistribute latency...
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0/GstFakeSink:fakesink0: sync = false
Got EOS from element "pipeline0".
Execution ended after 0:00:04.017670575
Setting pipeline to NULL ...
GST_ARGUS: Cleaning up
GST_ARGUS: Done Success
Freeing pipeline ...
gst-launch-1.0 nvarguscamerasrc sensor-id=1 sensor-mode=0 ! 'video/x-raw(memory:NVMM),width=3864, height=2192, framerate=60/1, format=NV12' ! nvvidconv ! fpsdisplaysink text-overlay=0 name=sink_0 video-sink=fakesink sync=0 -v
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0/GstFakeSink:fakesink0: sync = false
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
/GstPipeline:pipeline0/GstNvArgusCameraSrc:nvarguscamerasrc0.GstPad:src: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:src: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/Gstnvvconv:nvvconv0.GstPad:src: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0.GstGhostPad:sink.GstProxyPad:proxypad0: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0/GstFakeSink:fakesink0.GstPad:sink: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0.GstGhostPad:sink: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/Gstnvvconv:nvvconv0.GstPad:sink: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
/GstPipeline:pipeline0/GstCapsFilter:capsfilter0.GstPad:sink: caps = video/x-raw(memory:NVMM), width=(int)3864, height=(int)2192, format=(string)NV12, framerate=(fraction)60/1
GST_ARGUS: Creating output stream
CONSUMER: Waiting until producer is connected...
GST_ARGUS: Available Sensor modes :
GST_ARGUS: 3864 x 2192 FR = 90.000001 fps Duration = 11111111 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 22000, max 660000000;

GST_ARGUS: 1296 x 720 FR = 260.000057 fps Duration = 3846153 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 22000, max 660000000;

GST_ARGUS: 1920 x 1080 FR = 90.000001 fps Duration = 11111111 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 22000, max 660000000;

GST_ARGUS: 3864 x 2192 FR = 59.999999 fps Duration = 16666667 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 32000, max 660000000;

GST_ARGUS: 1296 x 720 FR = 174.000013 fps Duration = 5747126 ; Analog Gain range min 1.000000, max 3981.070801; Exposure Range min 32000, max 660000000;

GST_ARGUS: Running with following settings:
   Camera index = 1
   Camera mode  = 0
   Output Stream W = 3864 H = 2192
   seconds to Run    = 0
   Frame Rate = 90.000001
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadExecute:734 NvBufSurfaceFromFd Failed.
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadFunction:245 (propagating)
Redistribute latency...
/GstPipeline:pipeline0/GstFPSDisplaySink:sink_0/GstFakeSink:fakesink0: sync = false
Got EOS from element "pipeline0".
Execution ended after 0:00:04.011631005
Setting pipeline to NULL ...
GST_ARGUS: Cleaning up
GST_ARGUS: Done Success
Freeing pipeline ...

Based on the results, would it be possible that I’m using some “outdated” argus version that doesn’t support the newer JerPack version? Seems the error is coming from libargus.

hello calvin0328,

please try again with below commands to boost all the VI/CSI/ISP clocks.
for instance,

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

Hi Jerry,

I didn’t see there is any difference after boost all the frequency. I also turned on the jetson_clocks. The issue still existed.

Best,
Wenhai.

hello calvin0328,

one thing strange here…
please double check the node under tegra-camera-platform{}, it should not disabled.
for instance,

		__overlay__ {
			tegra-camera-platform {
				compatible = "nvidia, tegra-camera-platform";
				num_csi_lanes = <8>;
				...
				modules {
					status = "okay";
					sensor_module0: module0 {
						status = "disabled";

					sensor_module1: module1 {
						status = "disabled";
...

Hi Jerry,

Just have a check, I noticed these parts under tegra234-p3767-camera-p3768-fr_fpa_a_p22-overlay will be overwritten by the corresponding sections under the individual camera dts files. For example, in tegra234-p3767-camera-p3768-fr_imx715-cam0-4lane-overlay, it wrote as:

...
	fragment@0 {
		target = <&sensor_module1>;
		__overlay__ {
			status = "okay";
			badge = "imx715_centerright_framos";
			drivernode0 {
				status = "okay";
				/* Declare PCL support driver (classically known as guid) */
				devname = "imx715 10-001a";
				/* Declare the device-tree hierarchy to driver instance */
				sysfs-device-tree = "/sys/firmware/devicetree/base/bus@0/cam_i2cmux/i2c@0/imx715_b@1a";
			};
		};
	};
...

Looks like those “disabled” have been set to okay in the individual sensor dts files.

hello calvin0328,

let’s gather debug logs from rce-fw,
please follow the steps to enable VI tracing logs.

modprobe rtcpu_debug    #for JP-6.1 or later.
echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 2 > /sys/kernel/debug/camrtc/log-level
echo > /sys/kernel/debug/tracing/trace
cat /sys/kernel/debug/tracing/trace

Hi Jerry,

This is the log after I run the gst-launch-1.0 command:

# tracer: nop
#
# entries-in-buffer/entries-written: 11/11   #P:6
#
#                                _-------=> irqs-off
#                               / _------=> need-resched
#                              | / _-----=> need-resched-lazy
#                              || / _----=> hardirq/softirq
#                              ||| / _---=> preempt-depth
#                              |||| / _--=> preempt-lazy-depth
#                              ||||| / _-=> migrate-disable
#                              |||||| /     delay
#           TASK-PID     CPU#  |||||||  TIMESTAMP  FUNCTION
#              | |         |   |||||||      |         |
     kworker/3:0-6868    [003] ....... 81833.906961: rtcpu_string: tstamp:2558025480848 id:0x04010000 str:"VM0 activating."
     kworker/3:0-6868    [003] ....... 81833.906965: rtcpu_dbg_set_loglevel: tstamp:2558025696022 old:2 new:2
     kworker/3:0-6868    [003] ....... 81840.066804: rtcpu_string: tstamp:2558219084160 id:0x04010000 str:"VM0 deactivating."
     kworker/3:0-6868    [003] ....... 81841.354779: rtcpu_string: tstamp:2558259102535 id:0x04010000 str:"VM0 activating."
     kworker/3:0-6868    [003] ....... 81841.690760: rtcpu_vinotify_event: tstamp:2558270265472 cch:1 vi:0 tag:VIFALC_TDSTATE channel:0x0b frame:0 vi_tstamp:81864648409600 data:0x799cc80010000000
     kworker/3:0-6868    [003] ....... 81841.690763: rtcpu_vinotify_event: tstamp:2558270265612 cch:1 vi:0 tag:VIFALC_TDSTATE channel:0x0b frame:0 vi_tstamp:81864648416000 data:0x0000000031000001
     kworker/3:0-6868    [003] ....... 81841.690763: rtcpu_vinotify_event: tstamp:2558270265769 cch:1 vi:0 tag:VIFALC_ACTIONLST channel:0x0b frame:0 vi_tstamp:81864648419072 data:0x0000000007020001
     kworker/3:0-6868    [003] ....... 81841.746758: rtcpu_vinotify_event: tstamp:2558270941632 cch:1 vi:0 tag:VIFALC_TDSTATE channel:0x0b frame:0 vi_tstamp:81864659882240 data:0x799cc50010000000
     kworker/3:0-6868    [003] ....... 81841.746758: rtcpu_vinotify_event: tstamp:2558270941791 cch:1 vi:0 tag:VIFALC_TDSTATE channel:0x0b frame:0 vi_tstamp:81864659889216 data:0x0000000031000002
     kworker/3:0-6868    [003] ....... 81846.454657: rtcpu_isp_falcon_task_start: tstamp:2912779248 ch:0 task:HANDLE_EVENT
     kworker/3:0-6868    [003] ....... 81846.454661: rtcpu_isp_falcon_task_end: tstamp:2912779283 task:HANDLE_EVENT

Then the following is for the other camera:

# tracer: nop
#
# entries-in-buffer/entries-written: 9/9   #P:6
#
#                                _-------=> irqs-off
#                               / _------=> need-resched
#                              | / _-----=> need-resched-lazy
#                              || / _----=> hardirq/softirq
#                              ||| / _---=> preempt-depth
#                              |||| / _--=> preempt-lazy-depth
#                              ||||| / _-=> migrate-disable
#                              |||||| /     delay
#           TASK-PID     CPU#  |||||||  TIMESTAMP  FUNCTION
#              | |         |   |||||||      |         |
     kworker/3:0-6868    [003] ....... 81923.072775: rtcpu_string: tstamp:2560811895925 id:0x04010000 str:"VM0 deactivating."
     kworker/3:0-6868    [003] ....... 81930.020615: rtcpu_string: tstamp:2561030210467 id:0x04010000 str:"VM0 activating."
     kworker/3:0-6868    [003] ....... 81930.360604: rtcpu_vinotify_event: tstamp:2561040541326 cch:1 vi:1 tag:VIFALC_TDSTATE channel:0x0b frame:0 vi_tstamp:81953297104704 data:0x799da00010000000
     kworker/3:0-6868    [003] ....... 81930.360606: rtcpu_vinotify_event: tstamp:2561040541481 cch:1 vi:1 tag:VIFALC_TDSTATE channel:0x0b frame:0 vi_tstamp:81953297111104 data:0x0000000031000001
     kworker/3:0-6868    [003] ....... 81930.360607: rtcpu_vinotify_event: tstamp:2561040541635 cch:1 vi:1 tag:VIFALC_ACTIONLST channel:0x0b frame:0 vi_tstamp:81953297114144 data:0x0000000007020001
     kworker/3:0-6868    [003] ....... 81930.360607: rtcpu_vinotify_event: tstamp:2561041217365 cch:1 vi:1 tag:VIFALC_TDSTATE channel:0x0b frame:0 vi_tstamp:81953310893696 data:0x799d9d0010000000
     kworker/3:0-6868    [003] ....... 81930.360608: rtcpu_vinotify_event: tstamp:2561041217522 cch:1 vi:1 tag:VIFALC_TDSTATE channel:0x0b frame:0 vi_tstamp:81953310900160 data:0x0000000031000002
     kworker/3:0-6868    [003] ....... 81935.020493: rtcpu_isp_falcon_task_start: tstamp:1385926516 ch:0 task:HANDLE_EVENT
     kworker/3:0-6868    [003] ....... 81935.020497: rtcpu_isp_falcon_task_end: tstamp:1385926550 task:HANDLE_EVENT

hello calvin0328,

it looks there’s no validate frames on the CSI channel.
let me give you VI tracing logs with a success image capture as an example.
here must be one pair of CHANSEL_PXL_SOF/CHANSEL_PXL_EOF to indicate a frame has detected by VI engine.
afterwards, it’s ATOMP_FRAME_DONE to indicate it’s complete writing a frame to memory.
for instance,

rtcpu_vinotify_event: tstamp:4058867917 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:129874754944 data:0x0000000000000001
rtcpu_vinotify_event: tstamp:4059206674 cch:0 vi:0 tag:ATOMP_FS channel:0x00 frame:1 vi_tstamp:129891804896 data:0x0000000800000000
rtcpu_vinotify_event: tstamp:4059206818 cch:0 vi:0 tag:CHANSEL_PXL_SOF channel:0x23 frame:1 vi_tstamp:129891808928 data:0x0000000000000001
rtcpu_vinotify_event: tstamp:4059206976 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:1 vi_tstamp:129891815424 data:0x0000000008020001
rtcpu_vinotify_error: tstamp:4060164160 cch:0 vi:0 tag:CSIMUX_FRAME channel:0x00 frame:1 vi_tstamp:129925171392 data:0x00000000000000a0
rtcpu_vinotify_event: tstamp:4060166846 cch:0 vi:0 tag:CHANSEL_PXL_EOF channel:0x23 frame:1 vi_tstamp:129923836800 data:0x0000000004370002
rtcpu_vinotify_event: tstamp:4060167015 cch:0 vi:0 tag:ATOMP_FRAME_DONE channel:0x23 frame:1 vi_tstamp:129923837312 data:0x0000000000000000

let’s refer to developer guide, Sensor Pixel Clock, and SerDes Pixel Clock to examine your clock rate settings, which must be set correctly to avoid potential issues.

Hi Jerry,

If I can successfully receive the raw data in a correct FPS, then the data is also correct. Would there still be an issue with this pxl clk settings? One more thing I forgot to mention, I am using a JNX42 customized board, and the previous working environment is JetPack 5.1.3. The sensor clock settings are the same with what I used right now on JetPack 6.2, but this time I can’t stream any frame via libargus, passing by the ISP. Is there anything that I can do further investigation? Thanks!

Best,
Wenhai.

hello calvin0328,

is it porting issue?
please see-also developer guide, Camera Driver Porting to review your sensor driver.
besides, you may check Topic 310858 for some known changes when porting DTS from JP-5 to JP-6.