7425 - Radiant: How to use Synplify Pro on one file, and LSE on another in the same design?

• Related Articles

• 6142 - Lattice Diamond: Why LSE and Synplify Pro has different RTL View implementation?

  LSE and Synplify Pro use different parsers to parse the design files. LSE uses Verific parser, a third-party tool for Lattice, and the same is used by Netlist Analyzer to infer the RTL view. Synplify Pro uses its own parser, and HDL Analyst uses this ...

• 7562 - Radiant: The synthesis design process does not complete when synthesis is run on Synplify Pro OEM

  In Radiant, the synthesis and post-synthesis processes are a combined process under "Synthesize Design". When you run synthesis using the standalone version of Synplify Pro, this version generates a .vm file which will be used to run post-synthesis ...

• 6787 - Radiant: Is it recommended to check the initial timing report generated by Synplify Pro under the SRR file?

  Customers should not be using the timing report generated by Synplify Pro. There is a warning on the Synplify Pro timing report to refer to the FPGA vendor place and route report. See the warning below: Please use the timing report generated by ...

• 2353 - All FPGAs: What is the function of the Synplify Pro's option "Fix Generated Clocks"?

  Description: The option is used for the generated-clock conversion. i.e., its values are * 0 – does not convert * 1 – converts; does not report * 2 – converts; reports only sequential elements that could not be converted * 3 (default) – converts; ...

• 7136 - Diamond: What is the usage of the synthesis strategy setting "Frequency" of Synplify Pro/Lattice LSE?

  The frequency setting only applies to clocks with undefined frequencies through the SDC constraints create_clock and create_generated_clock constraints. As observed in the screenshots, Synplify Pro accepts SDC constraints through the Synthesis ...