Integration of new camera sensor - No cameras available issue

After including --set ctrl bypass_mode=0 we were able to read the frames.

Here is the trace logtracelogs (17.3 KB)

what does “rtos_queue_peek_from_isr_failed” mean?

The second frame got short frame error that tell the output line didn’t as expected.

 kworker/0:1-14102 [000] ....  6359.080687: rtcpu_vinotify_event: tstamp:199047013074 tag:ATOMP_FS channel:0x00 frame:2 vi_tstamp:199046678250 data:0x00000000
     kworker/0:1-14102 [000] ....  6359.080689: rtcpu_vinotify_event: tstamp:199047013238 tag:CHANSEL_PXL_SOF channel:0x23 frame:2 vi_tstamp:199046686236 data:0x00000001
     kworker/0:1-14102 [000] ....  6359.080690: rtcpu_vinotify_event: tstamp:199047013375 tag:RESERVED_19 channel:0x23 frame:2 vi_tstamp:197625959424 data:0x08020002
     kworker/0:1-14102 [000] ....  6359.080691: rtcpu_vinotify_event: tstamp:199047013533 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:197626137536 data:0x10000000
     kworker/0:1-14102 [000] ....  6359.080693: rtcpu_vinotify_event: tstamp:199047013668 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:197626167264 data:0x31000003
     kworker/0:1-14102 [000] ....  6359.080695: rtcpu_vinotify_event: tstamp:199047410045 tag:CHANSEL_PXL_EOF channel:0x23 frame:2 vi_tstamp:199047196159 data:0x043f0002
     kworker/0:1-14102 [000] ....  6359.080696: rtcpu_vinotify_event: tstamp:199047410185 tag:FE channel:0x00 frame:2 vi_tstamp:199047196183 data:0x00000020
     kworker/0:1-14102 [000] ....  6359.080697: rtcpu_vinotify_event: tstamp:199047410346 tag:ATOMP_FE channel:0x00 frame:2 vi_tstamp:199047196185 data:0x00000000
     kworker/0:1-14102 [000] ....  6359.080699: rtcpu_vinotify_event: tstamp:199047410482 tag:ATOMP_FRAME_DONE channel:0x23 frame:2 vi_tstamp:199047196195 data:0x00000000
     kworker/0:1-14102 [000] ....  6359.080700: rtcpu_vinotify_event: tstamp:199047410642 tag:RESERVED_19 channel:0x23 frame:2 vi_tstamp:197642293920 data:0x02020002
     kworker/0:1-14102 [000] ....  6359.080701: rtcpu_vinotify_event: tstamp:199047410778 tag:RESERVED_19 channel:0x23 frame:2 vi_tstamp:197642306176 data:0x00020002
     kworker/0:1-14102 [000] ....  6359.080703: rtcpu_vinotify_event: tstamp:199047410936 tag:RESERVED_19 channel:0x23 frame:0 vi_tstamp:197642328000 data:0x07020003
     kworker/0:1-14102 [000] ....  6359.080704: rtcpu_vinotify_event: tstamp:199047411071 tag:FS channel:0x00 frame:3 vi_tstamp:199047404790 data:0x00000010
     kworker/0:1-14102 [000] ....  6359.080705: rtcpu_vinotify_event: tstamp:199047411233 tag:ATOMP_FS channel:0x00 frame:3 vi_tstamp:199047404792 data:0x00000000
     kworker/0:1-14102 [000] ....  6359.080706: rtcpu_vinotify_event: tstamp:199047411366 tag:FE channel:0x00 frame:3 vi_tstamp:199047404803 data:0x00000020



     kworker/0:1-14102 [000] ....  6359.080708: rtcpu_vinotify_event: tstamp:199047935019 tag:CHANSEL_SHORT_FRAME channel:0x01 frame:3 vi_tstamp:199047404804 data:0x01000000

can u please tell what more information is required?

Does the ov5693.ko are the same file that rmmod and insmod?

yes

Could you check more times to check if can repo the symptom every reboot?

ok will check and update here

I tried rebooting 9 times.
4 th time video0 didnt get enumerated.

remaining times it was same, only after rmmod and insmod we are getting perfect image

Could you check if any power/reset/ … pin status before and after the rmmod/insmod

Right now we are force loading our camera driver.

How to enable hot plug for our custom mipi camera driver so that when camera is inserted then driver automatically gets loaded and when removed the driver gets unloaded Instead of forceloading driver.

There’s no hotplug supported for Jetson camera framework, sorry.