5606 - CrossLink: When confirming by simulation for CMOS-to-DPHY IP, 16-bit Short Packet Data Filed is output as follows 0,1,0,1,0,1,0,1...... Is this correct?

Description:

With regards to frame synchronization, you may refer to section 9.8.1 Frame Synchronization Packets of mipi CSI-2 specification. It states that each image frame shall begin with a Frame Start (FS) Packet containing the Frame Start Code which is 0x00 and Framed End Packet containing Frame End Code which is 0x01. The FS and FE synchronization packets the Short Packet Data Field shall contain a 16-bit frame number and shall be non-zero to distinguish it from the use-case where fame number is inoperative and remains set to zero. The 0 that you observed is actually the Frame Start Code and 1 is the frame number. Furthermore, frame number increments by 1 for every Frame Start packet with same Virtual Channel and is periodically reset to one.

Related Articles
5924 - D-PHY to CMOS v1.2/CrossLink: Why does the DPHY RX channel signal did not move from LP to HS mode?
This is due to metastability encountered in v1.2. It is recommended to upgrade to DPHY to CMOS v1.3 with the corresponding IP fix.
6114 - Crosslink NX : Are there any Reference Designs of DPHY for different applications as stated below? 1. Connecting Soft DPHY Rx module output to Soft DPHY Tx module input. 2. Image acquisition from a camera through Hard DPHY.
Solution: The following RDs available for Crosslink-NX will support the said applications: 1. FPGA-RD-02212 : N Input to 1 Output MIPI CSI-2 Side-by-Side Aggregation - Aggregate multiple Image Sensors into a single Output with Minimal Latency. - Uses ...
5777 - [CrossLink] [MIPI D-PHY to CMOS Interface Bridge IP]: What can be the cause of frequency calculation error in DPHY to CMOS GPLL after clicking the 'Calculate PLL Frequencies' button of the DPHY-to-CMOS v1.3 Clarity GUI with provided configuration
With regards to D-PHY to CMOS v1.3 GUI, if the user happens to encounter the dialogue prompt saying that "the desired frequencies for this configuration could not be generated by the PLL", it means that it is not a recommended value that will be used ...
5424 - CMOS-TO-DPHY IP: Why does the connection type is still "pad-pin"declared in Clarity even if the signal does not go to I/O pins but rather go to internal logic?
Solution Clarity Designer builder for modules and IP such as cmos-to-dphy is intended to be stand alone and thus it automatically generates a pad-pin type of connection. It is already a known issue when this IP module is used or connected as part of ...
4269 - [ECP5/ECP5-5G]: Is it possible to have a 16 bit data path using Lattice SGMII (Serial Gigabit Media Independent Interface ) IP?
The SGMII IP supports 8-bit data path. It is not possible to use 16 bit data path with this IP.

5606 - CrossLink: When confirming by simulation for CMOS-to-DPHY IP, 16-bit Short Packet Data Filed is output as follows 0,1,0,1,0,1,0,1...... Is this correct?

5606 - CrossLink: When confirming by simulation for CMOS-to-DPHY IP, 16-bit Short Packet Data Filed is output as follows 0,1,0,1,0,1,0,1...... Is this correct?

Related Articles

5924 - D-PHY to CMOS v1.2/CrossLink: Why does the DPHY RX channel signal did not move from LP to HS mode?

6114 - Crosslink NX : Are there any Reference Designs of DPHY for different applications as stated below? 1. Connecting Soft DPHY Rx module output to Soft DPHY Tx module input. 2. Image acquisition from a camera through Hard DPHY.

5777 - [CrossLink] [MIPI D-PHY to CMOS Interface Bridge IP]: What can be the cause of frequency calculation error in DPHY to CMOS GPLL after clicking the 'Calculate PLL Frequencies' button of the DPHY-to-CMOS v1.3 Clarity GUI with provided configuration

5424 - CMOS-TO-DPHY IP: Why does the connection type is still "pad-pin"declared in Clarity even if the signal does not go to I/O pins but rather go to internal logic?

4269 - [ECP5/ECP5-5G]: Is it possible to have a 16 bit data path using Lattice SGMII (Serial Gigabit Media Independent Interface ) IP?