I am working with a Jetson Xavier NX and using Jetpack version 5.1.3. I am streaming camera data to the device and would like to verify whether frames are being received at the video nodes at the kernel level. Since the processor can support virtual channels, we want to know if one or both virtual channels are being received properly.
Could anyone provide guidance on how to check if the camera frames are being captured or processed correctly from the virtual channels? Any suggestions or tools I should use for this?
I would like to inform that I don’t have nay issues in bringing up the sensor, as of now I could able to stream without any issues.
As of now I’m looking for following issue:
In certain scenarios, the camera stops streaming. When this happens, reconfiguring the sensor allows me to resume the stream.
What I want to do now is to detect that frames are not coming within the kernel so that whenever frames don’t come, kernel has to send interrupt to my driver so that I can reconfigure.
we tried to debug files under Linux_for_Tegra/sources/kernel/nvidia/drivers/media/platform/tegra/camera/vi/ but we could not able identify.
Any suggestions on how to monitor this at the kernel level?
Thank you for your suggestion earlier. It was really helpful, and I was able to detect when frames are not being received by monitoring the **tegra_channel_error_recover**() function.
However, I have another question. I am currently working with two nodes, and I would like to know which specific node is not receiving frames. Could you suggest a way to identify the problematic node at the kernel level?
Thank you for your help! It worked perfectly. Now, I was wondering if you could kindly assist me with sending an interrupt from tegra_channel_error_recover to Linux_for_Tegra/sources/kernel/nvidia/drivers/media/i2c/ driver . I would greatly appreciate your guidance on how to achieve this.
The tegra_channel_error_recover function is being triggered whenever streaming is halted. However, this function keeps getting called repeatedly, which leads to the sensor being reconfigured multiple times.