Oh and I am not sure if it helps but looking into the capture_status.status for the corr_err the value is 14, ie. CAPTURE_STATUS_FALCON_ERROR.
There are CHANSEL_NOMATCH in stream mmap could be incorrect embedded_data_height in device tree cause that.
And in the webui have short frame could be incorrect output lines cause that.
What’s the different for this two logs?
Boost the clocks to try.
sudo su
echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/isp/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate
I do not set embedded_data_height in my dev tree anywhere, also prepping the nvidia BSP sources I am not seeing any examples anywhere.
As for my clocks, they are all already at max except for the emc.
I am not sure if I understand your question about the difference in the logs. The one labeled cartken_webui is the one from running our webui that shows 4xstreams at a time and then switches between wither RGB or depth cameras and the other log is from tunning v4l2-ctl.
Could you mean embedded_metadata_height?
Have a check below link.
According to the information I have our metadata heights are set correctly. I am not able to see from the trace what the cause would be when going through the documentation you suggested.
Could you elaborate on this and where I should look to find a solution?
The short frame tell NVCSI/VI receive less lines than expected.
You need to check the sensor configuration.
Thanks
I will reach out to our suppliers for that information. While I wait for them to reply is there anything else that could be the cause?
I have contacted our suppliers and it seems that all heights and metadata properties have been set correctly. Is there anything else that could be causing these errors?