Part Number: TDA4VM-Q1
Other Parts Discussed in Thread: TDA4VM
Tool/software:
Hi experts,
Our customers is encountering an issue with the CSI-TX output configuration on the TDA4VM when interfacing with a Maxim SerDes chip (MAX96755).
Here is the background of the problem:
-
System Setup: We are using the TDA4VM's CSI-TX interface configured for DSI output to transmit rendered images externally via a SerDes link. The physical hardware chain is as follows:
-
TDA4 Interface: We are using the TDA4VM's CSI-TX block to output the display data to the MAX96755 serializer.
-
Software Implementation: The CSI-TX output configuration and data streaming as below.
-
Observed Phenomenon:
-
The MAX96755 (Serializer) and MAX96752 (Deserializer) successfully establish a link, and video data is being transferred across the SerDes connection.
-
However, the LVDS signal output by the MAX96752 (after deserialization) is incomplete or corrupted.
-
Reading register 0x3A0 (DSI Controller Status) on the MAX96755 serializer indicates the presence of DSI ECC errors (specifically "ECC one-bit error" and "ECC two or more bits error").
-
-
Request from Maxim: Following advice from the Maxim, customer need to understand how the TDA4VM configures and controls the following specific low-level DSI operational modes. The screenshot below shows these modes, which also correspond to the default settings of the MAX96755:
-
Transmission Packet: Enable / Disable EoTp (End of Transmission Packet)
-
Packet Types: Blanking / Null Packets (during blanking intervals)
-
DSI Video Mode: Non-Burst With Sync Pulses / Non-Burst With Sync Events
-
-
My Question: I have searched within the TI SDK (presumably through the tivxCsitxNode configuration parameters and related documentation) but cannot find explicit options to configure these specific DSI modes (EoTp, Blanking/Null packets, Sync Pulses/Events). I suspect these low-level protocol settings might be managed deeper within the DSI/CSI-TX driver stack based on higher-level configurations (like display timings) and are not directly exposed through the API.
Could you please clarify how the TDA4VM's DSI driver stack implements or determines these specific DSI operational modes when using the CSI-TX peripheral for DSI video output?
