C
REATING
C
USTOM
C
OMPONENTS
IN
L
ATTICE
M
ICO
S
YSTEM
:
Creating the Verilog Wrapper for VHDL Designs
LatticeMico32 Hardware Developer User Guide
89
Pointing to the Correct .ngo File
You must enable the Translate Design step to use the correct .ngo file of the
VHDL-based component that was created in an earlier step.
To point to the correct .ngo file:
1. Copy the .ngo file to the \soc directory, located in the LatticeMico32
platform project directory.
2. In Diamond, choose
Project > Property Pages
.
3. In the Macro Path box of the Project Properties dialog box, provide the
path to the LatticeMico32 Platform project's \soc directory that contains
the .ngo file copied in step 1. You can provide an absolute or relative path.
For example, an absolute path might be
c:\ispTOOLS<
version
>\examples\VHDL_Test\LM32_Platform\soc.
A relative path would be a path relative to the Diamond project directory.
For example, if the LatticeMico32 platform project directory is contained in
the Diamond project, the relative path might be
.\LM32_platform\soc
If the Diamond project is contained in the LatticeMico32 platform project
directory, the relative path would be simply
.\soc
Figure 45: Verilog Black-Box Definition of a VHDL Custom Component
module vhdl_custom (
// wishbone slave signals
input[31:0] ADR_I,
input[31:0] DAT_I,
input WE_I,
input[3:0] SEL_I,
input STB_I,
input CYC_I,
input LOCK_I,
input[2:0] CTI_I,
input[1:0] BTE_I,
output[31:0] DAT_O,
output ACK_O,
// external signals
output [30:0] custom_ext,
inout [30:0] custom_ext_io,
input CLK_I,
input RST_I,
output INTR_O )/*synthesis syn_black_box
black_box_pad_pin = “custom_ext_io[30:0]” */;
endmodule
