Tool/software:
Team,
I pointed the customer to devmon2 to read the CSI error register. It gives them the same results weather it is function or not. Would this point the static issue being a different problem?
You can see below, the address for the register returned 0x00000000. We tested it under normal operating conditions and when we had the camera outputting static video and results the same. Is this the expected returned value if everything is working correctly? Does this indicate that the MIPI connection between our decoder and the TDA4 is good? If there are other areas we should look at, please let me know.
root@ccids:~# devmem2 0x04504110
/dev/mem opened.
Memory mapped at address 0xffffa7bf0000.
Read at address 0x04504110 (0xffffa7bf4110): 0x00000000
Initial inquiry which I responded for devmon2:
We are chasing down some issues with our product that uses the TDA4VM. This system has 4 cameras that send TVI data to a Techpoint TP2855 Decoder, which then sends the data via MIPI to the TDA4VM. The issue we have had is with camera video being displayed as static. We have identified a potential problem with the cameras themselves, were the camera is what sends out the static video, but we want to verify there is no other possible failure mode.
In the reference manual for the TDA4VM, I see it mentioned that there is a lot of CSI error registers and interrupts that can trigger if an error is detected. Our thought was we can look at these to see if there are any CSI issues. However, even when the video being received is static, these errors/events aren’t triggered. The team first wanted to confirm with you guys that this feature is actually implemented in the driver? In addition, if there are any config settings the TDA4VM team think we should check to verify the connection is good, please let us know.
Please advise!
Thanks,
Jason
