nvcsi on the JetsonTX2 for custom driver

hi helloworld123456,

about the failure, you should ignore below since it’s bandwidth calculation warning.

tegra-vi4 15700000.vi: WAR:Calculation not precise.Ignore BW request failure

however, this failure shows that VI driver did not receive start of frame signaling.

tegra-vi4 15700000.vi: PXL_SOF syncpt timeout! err = -11

your VI tracing messages also not including VI drivers initialization function calls. you should saw messages with rtcpu_vinotify_handle_msg workers.
could you please co-working with your hardware engineer to probe the MIPI signaling, you should also checking the regulator settings. thanks

the signal should look as this documents states.
https://www.analog.com/media/en/technical-documentation/application-notes/an-1337.pdf
I can see the signals similarly as described in the document except for when it timeouts which causes an impedance change and the signal to fluctuate.

When I run the v4l2-compliance test, I don’t get any failures. we had to make some changes to the VI source code. I can’t remember the changes anymore. But the "PXL_SOF syncpt timeout! err = -11 " issue still showing every time. I started a tread for the issue see below:
https://devtalk.nvidia.com/default/topic/1046667/jetson-tx2/csi-camera-driver-fro-adv7280-m-pxl_sof-syncpt-timeout-11/post/5311334/#5311334

@JerryChang,
Any ideas on the software side how to debug the “PXL_SOF syncpt timeout! err = -11”

@JerryChang
Let me add that I thought we had an hardware issue, so we are now tests on the development kit for the encoder, https://www.digikey.com/catalog/en/partgroup/adv7280-m-evaluation-board/47397

We are still seeing the same issue of “PXL_SOF syncpt timeout! err = -11”

How long does it take for your sensor to start sending data? If it takes more than 1500 ms from when s_stream is called to when the data arrives you’ll see a failure. I can’t recall if that manifests as PXL_SOF syncpt timeout error but I would assume that it would.

Hi nicolas.norena:
After checking the pdf which you added in the comment #22, It said that MIPI CSI data signal should be 1.2V,0.3V,0.1V,or 0V, but our deteted wave is 0.8V, what about yours? Do we need to review the Hardware design again with the HW engineers?

Sincerely.
Thanks very much.

hello nicolas.norena,

you may refer to https://elinux.org/Jetson_TX2_Camera_BringUp for some debug tips.
thanks

I can’t find the ov5693.c in the 32.2 source files. The development guide says that the reference is imx185_1.c, and I can’t find it too…
The adv7180.c driver in the sources is not ready to be used in TX2?

Thanks