Image Artifacts from Camera

[sarah.graham]

I am having random image artifacts with my custom camera similar to the post below. I am using R36.3 with an Jetson AGX Orin. Here is an example of the missing data:

Black stripes in raw image

Hello, I’m trying to capture images with two IMX264 modules (monochrome), using the recent 36.2 release (kernel 5.15). I’m using a custom carrier board with an Orin NX. The same board and cameras were tested successfully with the previous release so I know the hardware is OK. I receive almost good images, but I get a lot of black stripes. Changing the pix_clk_hz property and the csi/vi/etc clocks seems to impact the number of stripes, but I could not find a proper configuration to remove al…

Here is a trace for a single image:

kworker/9:2-7419 [009] … 75292.859111: rtcpu_vinotify_event: tstamp:2355493084327 cch:0 vi:0 tag:FS channel:0x00 frame:0 vi_tstamp:75375774452128 data:0x0000000000000010
kworker/9:2-7419 [009] … 75292.859113: rtcpu_vinotify_event: tstamp:2355493084493 cch:0 vi:0 tag:ATOMP_FS channel:0x00 frame:0 vi_tstamp:75375774452256 data:0x0000000800000000
kworker/9:2-7419 [009] … 75292.859114: rtcpu_vinotify_event: tstamp:2355493084628 cch:0 vi:0 tag:CHANSEL_PXL_SOF channel:0x23 frame:0 vi_tstamp:75375774455488 data:0x0000000000000001
kworker/9:2-7419 [009] … 75292.859115: rtcpu_vinotify_event: tstamp:2355493084778 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:75375774493184 data:0x0000000008020001
kworker/9:2-7419 [009] … 75292.859116: rtcpu_vinotify_event: tstamp:2355493480813 cch:0 vi:0 tag:CHANSEL_PXL_EOF channel:0x23 frame:0 vi_tstamp:75375785774080 data:0x0000000005230002
kworker/9:2-7419 [009] … 75292.859116: rtcpu_vinotify_event: tstamp:2355493480970 cch:0 vi:0 tag:ATOMP_FRAME_DONE channel:0x23 frame:0 vi_tstamp:75375785775040 data:0x0000000000000000
kworker/9:2-7419 [009] … 75292.859117: rtcpu_vinotify_event: tstamp:2355493481105 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:75375785797696 data:0x0000000002020001
kworker/9:2-7419 [009] … 75292.859118: rtcpu_vinotify_event: tstamp:2355493481254 cch:0 vi:0 tag:FE channel:0x00 frame:0 vi_tstamp:75375785775104 data:0x0000000000000020
kworker/9:2-7419 [009] … 75292.859118: rtcpu_vinotify_event: tstamp:2355493481390 cch:0 vi:0 tag:ATOMP_FE channel:0x00 frame:0 vi_tstamp:75375785775200 data:0x0000000800000000
kworker/9:2-7419 [009] … 75292.859119: rtcpu_vinotify_event: tstamp:2355493481543 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:75375785841664 data:0x000000000a020001
kworker/9:2-7419 [009] … 75292.859120: rtcpu_vinotify_event: tstamp:2355493481677 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:75375785846592 data:0x0000000000020001
kworker/9:2-7419 [009] … 75292.859120: rtcpu_vinotify_event: tstamp:2355493481827 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:75375785884640 data:0x0000000007020002
kworker/9:2-7419 [009] … 75292.859121: rtcpu_vinotify_event: tstamp:2355493481969 cch:0 vi:0 tag:FS channel:0x00 frame:0 vi_tstamp:75375791119136 data:0x0000000000000010

[JerryChang]

hello sarah.graham,

it’s Jetpack-6.0/r36.3 known issue,
please see-also Topic 299834 to apply the bug fixes.