
MIPI DSI to OpenLDI/FPD-Link/LVDS Interface Bridge Soft IP
User Guide
© 2016 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at
. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
24
FPGA-IPUG-02003-1.2
Figure 4.8. DSI Model Video Data
4.8.
Instantiating the IP
The core modules of MIPI DSI to OpenLDI/FPD-Link/LVDS Interface Bridge IP are synthesized and provided in NGO
format with black box Verilog source files for synthesis. Verilog source files named
<instance_name>_dsi_2_fpd_link_ip.v
and
<instance_name>_dphy_2_cmos_ip.v
instantiate the black
box of core modules. The top-level file
<instance_name>.v
instantiates
<instance_name>_dsi_2_fpd_link_ip.v
, OSC and PLL components.
The IP instances do not need to be instantiated one by one manually. The top-level file and the other Verilog source
files are provided in
\<project_dir>
. These files are refreshed each time the IP is regenerated.
A Verilog instance template
<instance_name>_inst.v
or VHDL instance template
<instance_name>_inst.vhd
is
also provided as a guide if the design is to be included in another top level module.
4.9.
Synthesizing and Implementing the IP
In Clarity Designer, the Clarity Designer project file (.sbx) is added to Lattice Diamond as a source file after IP is
generated. All required Verilog source files for implementation are invoked automatically. The IP can be directly
synthesized, mapped and placed/routed in the Diamond design environment after the IP is generated. Note that
default Diamond strategy (.sty) and default Diamond preference file (.lpf) are used. When using the .sbx approach,
import the recommended strategy and preferences from
\<project_dir>\dsi2fpdlink_eval\<instance_name>\impl\lifmd\lse
or
\<project_dir>\dsi2fpdlink_eval\<instance_name>\impl\lifmd\synplify
directories and set them as
active strategy and active preference file.