![Lattice Semiconductor LatticeMico32 Скачать руководство пользователя страница 38](http://html1.mh-extra.com/html/lattice-semiconductor/latticemico32/latticemico32_hardware-developer-user-manual_3843852038.webp)
U
SING
THE
L
ATTICE
M
ICO
S
YSTEM
S
OFTWARE
:
Creating the Microprocessor Platform in MSB
32
LatticeMico32 Hardware Developer User Guide
Flow for Verilog users – The <
platform_name
>.v file is used in both
simulation and implementation. It instantiates all the selected
components and the interconnect described in the MSB graphical user
interface. This file is the top-level simulation and synthesis RTL file
passed to Diamond. It includes the .v files for each component in the
design, which are used to synthesize and generate a bitstream to be
downloaded to the FPGA. The .v files for each component reside
under the top-level <
platform_name
>.v file.
Flow for VHDL users – The <
platform_name
>.v file is used in
simulation and implementation. If “Create VHDL NGO File” has been
selected, the <platform_name>.v file is used for simulation only, and
the <
platform_name
>_vhd.vhd file is used for implementation. In the
NGO flow, the <
platform_name
> component is instantiated as a black
box, and this instantiation is then automatically combined with the
<
platform_name
>.ngo file after synthesis to complete the
implementation netlist.
A mixed-mode Verilog and VHDL simulator is needed for functional
simulation in the flow for VHDL users.
A <
platform_name
>_vhd.vhd (VHDL) file, if you selected the “Create
VHDL Wrapper” option in the New Platform Wizard dialog box. It is
intended to be used only to incorporate the Verilog-based platform into a
VHDL design. The <
platform_name
>_vhd.vhd file contains the top-level
design used for synthesis. This top-level design file instantiates the
<
platform_name
> component as a black box. If the optional “Create VHDL
NGO File” has been selected, the <platform_name>_vhd.vhd file is
combined with the <
platform_name
>.ngo file after synthesis to complete
the post-synthesis netlist. The common name <
platform_name
> is used to
make this association.
A <
platform_name
>.ngo file, which is a Diamond database file that is a
synthesized version of <
platform_name
>.v. This file is created if the
optional “Create VHDL NGO File” has been selected, along with “Create
VHDL Wrapper.” It contains the same design information as
<
platform_name
>.v. For more information on the .ngo file, see the
“Building Modular Projects Using NGO Flow” topic in the Diamond online
Help.
MSB generates a <
platform_name
>_inst.v file, which contains the Verilog
instantiation template to use in a design where the platform is not the top-level
module. For the VHDL user, no equivalent file is generated that contains the
component declaration and component instance/portmap template for the
platform wrapper <
platform_name
>_vhd.vhd. The generated
<
platform_name
>_vhd.vhd file can be used to create one, if required.
Figure 14 shows the instantiation template for the platform1 platform.