Specify top-level module in Lattice Diemond build script.
When building multi-source files the toolchain gets confused as to which module is top-level. This ensures that the build_name of the design is selected.
This commit is contained in:
parent
ef6c517dad
commit
ef511e7edc
|
@ -52,6 +52,7 @@ def _build_files(device, sources, vincpaths, build_name):
|
||||||
tcl.append("prj_impl option {include path} {\"" + path + "\"}")
|
tcl.append("prj_impl option {include path} {\"" + path + "\"}")
|
||||||
for filename, language, library in sources:
|
for filename, language, library in sources:
|
||||||
tcl.append("prj_src add \"" + filename + "\" -work " + library)
|
tcl.append("prj_src add \"" + filename + "\" -work " + library)
|
||||||
|
tcl.append("prj_impl option top \"{}\"".format(build_name))
|
||||||
tcl.append("prj_run Synthesis -impl implementation -forceOne")
|
tcl.append("prj_run Synthesis -impl implementation -forceOne")
|
||||||
tcl.append("prj_run Translate -impl implementation")
|
tcl.append("prj_run Translate -impl implementation")
|
||||||
tcl.append("prj_run Map -impl implementation")
|
tcl.append("prj_run Map -impl implementation")
|
||||||
|
|
Loading…
Reference in New Issue