Setup: custom carrier board with LI-IMX274 module. Jetpack 3.3 L4T 28.2.1
The primary question I have is how to diagnose this camera debug message:
kworker/4:0-30 [004] ...1 67.376126: rtos_queue_peek_from_isr_failed: tstamp:2435942087 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 67.376131: rtcpu_start: tstamp:2435948320
kworker/4:0-30 [004] ...1 67.428130: rtos_queue_peek_from_isr_failed: tstamp:2437905937 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 67.428133: rtos_queue_peek_from_isr_failed: tstamp:2438035602 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 67.428135: rtcpu_start: tstamp:2438038187
kworker/4:0-30 [004] ...1 67.584140: rtos_queue_peek_from_isr_failed: tstamp:2443036442 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 67.740173: rtos_queue_peek_from_isr_failed: tstamp:2448036955 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 67.896162: rtos_queue_peek_from_isr_failed: tstamp:2453037458 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 68.052164: rtos_queue_peek_from_isr_failed: tstamp:2458037965 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 68.208180: rtos_queue_peek_from_isr_failed: tstamp:2463038470 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 68.364181: rtos_queue_peek_from_isr_failed: tstamp:2468038978 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 68.520180: rtos_queue_peek_from_isr_failed: tstamp:2473039487 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 68.728158: rtos_queue_peek_from_isr_failed: tstamp:2478039992 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 68.884163: rtos_queue_peek_from_isr_failed: tstamp:2483040501 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 70.456010: rtos_queue_peek_from_isr_failed: tstamp:2533045561 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 70.608144: rtos_queue_peek_from_isr_failed: tstamp:2538046073 queue:0x0b4a3c58
kworker/4:0-30 [004] ...1 70.764195: rtos_queue_peek_from_isr_failed: tstamp:2543046581 queue:0x0b4a3c58
All carrier boards and IMX274 modules contain these messages, however some will only display a green/black image after a power cycle.
Additional info:
I applied patches 0001-4 for FE-syncpt, vi timestamp, revert VI-Improvements, and vi-mode-recov. These patches did not alleviate the rtos_queue_peek fail or the green/black screen issue.
this is output from the same device when it does power up correctly: it still has the rtos fail message.
_-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
kworker/4:2-222 [004] ...1 274.011907: rtcpu_vinotify_handle_msg: tstamp:8893292164 tag:CHANSEL_PXL_EOF channel:0x00 frame:0 vi_tstamp:303356922 data:0x04370002
kworker/4:2-222 [004] ...1 274.011911: rtcpu_vinotify_handle_msg: tstamp:8893292267 tag:ISPBUF_FE channel:0x00 frame:0 vi_tstamp:303357043 data:0x00000000
kworker/4:2-222 [004] ...1 274.011911: rtcpu_vinotify_handle_msg: tstamp:8894589376 tag:ISPBUF_FS channel:0x00 frame:0 vi_tstamp:304654366 data:0x00000000
kworker/4:2-222 [004] ...1 274.011912: rtcpu_vinotify_handle_msg: tstamp:8894591585 tag:CHANSEL_PXL_SOF channel:0x00 frame:0 vi_tstamp:304656595 data:0x00000001
kworker/4:2-222 [004] ...1 274.063942: rtcpu_vinotify_handle_msg: tstamp:8894835463 tag:CHANSEL_PXL_EOF channel:0x00 frame:0 vi_tstamp:304900222 data:0x04370002
kworker/4:2-222 [004] ...1 274.063946: rtcpu_vinotify_handle_msg: tstamp:8894835567 tag:ISPBUF_FE channel:0x00 frame:0 vi_tstamp:304900344 data:0x00000000
kworker/4:2-222 [004] ...1 274.063947: rtcpu_vinotify_handle_msg: tstamp:8896132671 tag:ISPBUF_FS channel:0x00 frame:0 vi_tstamp:306197667 data:0x00000000
kworker/4:2-222 [004] ...1 274.063948: rtcpu_vinotify_handle_msg: tstamp:8896134887 tag:CHANSEL_PXL_SOF channel:0x00 frame:0 vi_tstamp:306199895 data:0x00000001
kworker/4:2-222 [004] ...1 274.063951: rtos_queue_peek_from_isr_failed: tstamp:8896294735 queue:0x0b4a3c58
kworker/4:2-222 [004] ...1 274.063952: rtcpu_vinotify_handle_msg: tstamp:8896378761 tag:CHANSEL_PXL_EOF channel:0x00 frame:0 vi_tstamp:306443522 data:0x04370002
kworker/4:2-222 [004] ...1 274.063954: rtcpu_vinotify_handle_msg: tstamp:8896378865 tag:ISPBUF_FE channel:0x00 frame:0 vi_tstamp:306443644 data:0x00000000
kworker/4:2-222 [004] ...1 274.115958: rtcpu_vinotify_handle_msg: tstamp:8897675966 tag:ISPBUF_FS channel:0x00 frame:0 vi_tstamp:307740967 data:0x00000000
kworker/4:2-222 [004] ...1 274.115962: rtcpu_vinotify_handle_msg: tstamp:8897678201 tag:CHANSEL_PXL_SOF channel:0x00 frame:0 vi_tstamp:307743195 data:0x00000001
kworker/4:2-222 [004] ...1 274.115963: rtcpu_vinotify_handle_msg: tstamp:8897922064 tag:CHANSEL_PXL_EOF channel:0x00 frame:0 vi_tstamp:307986824 data:0x04370002
kworker/4:2-222 [004] ...1 274.115964: rtcpu_vinotify_handle_msg: tstamp:8897922169 tag:ISPBUF_FE channel:0x00 frame:0 vi_tstamp:307986945 data:0x00000000
kworker/4:2-222 [004] ...1 274.167925: rtcpu_vinotify_handle_msg: tstamp:8899219267 tag:ISPBUF_FS channel:0x00 frame:0 vi_tstamp:309284268 data:0x00000000
kworker/4:2-222 [004] ...1 274.167927: rtcpu_vinotify_handle_msg: tstamp:8899221492 tag:CHANSEL_PXL_SOF channel:0x00 frame:0 vi_tstamp:309286497 data:0x00000001
kworker/4:2-222 [004] ...1 274.167928: rtcpu_vinotify_handle_msg: tstamp:8899465365 tag:CHANSEL_PXL_EOF channel:0x00 frame:0 vi_tstamp:309530124 data:0x04370002
kworker/4:2-222 [004] ...1 274.167929: rtcpu_vinotify_handle_msg: tstamp:8899465467 tag:ISPBUF_FE channel:0x00 frame:0 vi_tstamp:309530245 data:0x00000000
kworker/4:2-222 [004] ...1 274.219936: rtcpu_vinotify_handle_msg: tstamp:8900762570 tag:ISPBUF_FS channel:0x00 frame:0 vi_tstamp:310827569 data:0x00000000
kworker/4:2-222 [004] ...1 274.219939: rtcpu_vinotify_handle_msg: tstamp:8900764789 tag:CHANSEL_PXL_SOF channel:0x00 frame:0 vi_tstamp:310829797 data:0x00000001
kworker/4:2-222 [004] ...1 274.219940: rtcpu_vinotify_handle_msg: tstamp:8901008664 tag:CHANSEL_PXL_EOF channel:0x00 frame:0 vi_tstamp:311073425 data:0x04370002
kworker/4:2-222 [004] ...1 274.219941: rtcpu_vinotify_handle_msg: tstamp:8901008766 tag:ISPBUF_FE channel:0x00 frame:0 vi_tstamp:311073547 data:0x00000000
kworker/4:2-222 [004] ...1 274.219943: rtos_queue_peek_from_isr_failed: tstamp:8901295235 queue:0x0b4a3c58
The first trace log show the nvcsi/vi didn’t receive any validate frame data from sensor.
I would suggest to consult with Leopard to provide the driver.
Thanks ShaneCCC,
The Leopard provided driver does work, just not on every power up. I suspect that it’s an issue with my power on sequence.