"no reply from camera processor" from Custom IMX335 Camera

This is a follow-up post to Device Tree Settings. I’m currently in the testing phase of the IMX335 integration. My setup is Jetson Xavier NX sitting on Seeed’s A205 carrier board running Jetson Linux R32.6.1. I based my camera development (driver, mode table, and device tree) on the natively integrated IMX219. I confirmed the MIPI CSI-2 output from the IMX335 on an oscilloscope, so there is reason to believe that the camera hardware is built correctly and the Jetson is programming the image sensor over I2C properly. However, I’m still getting the “no reply from camera processor” error in dmesg and the “rtos_queue_peek_from_isr_failed” message in the trace log. What could be the cause of this?

If there no any validate symbol from trace log that could tell NVCSI/VI didn’t receive any data from sensor. You may need to probe the sensor signal to confirm it.


Thanks for the quick reply, I did verify sensor output using an oscilloscope.
imx335_20ms.pdf (58.3 KB) (one clock lane and one data lane shown)
What else can cause the Jetson to not recognize a raw bit stream from the sensor?

Confirm the port-index/bus-width configure in device tree.

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