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 inside Radiant.
When the user runs in the standalone Synplify Pro, and then switches to Radiant, Radiant checks the time stamp of the //_.vm file. If the .vm file is newer than all RTL source files & pre-synthesis constraint files, Radiant resumes from 'postsyn'. If the .vm file doesn't exist or is older than any input RTL source and pre-synthesis constraint file, Radiant will resume from Synplify Pro. Please check the .vm file timestamp in your case.
For Example:
1) You ran the Synthesis on the Synplify Pro OEM by clicking RUN
2) This will generate a .vm file under the Design implementation folder.
Looking into the RTL which is older than the generated .vm file
3) When you try to Ran now on the GUI it will only run Post-Syn (To check this, the .vm file should not be overwritten and should have the same date)
As you can see, under synplify pro report, it still uses the older data taken from Synplify Pro OEM and .vm file is not overwritten.
Note: If you try to "Force Run" the synthesis process it will rerun the whole Synthesis process. If you only desire to run post syn with the existing results from Synplify Pro Oem, just select the "Run Synthesis" or Click the "Synthesize Design" button.
Related Articles
6239 - Synplify Pro: Where to get the detailed information regarding the error code in synthesis?
Description: After synthesizing the design files while setting the SynplifyPro as synthesis tool, Radiant environment will provide the warnings and errors seen by the synthesis tool, however, detailed information can only be provided inside the ...6785 - Radiant / Synplify Pro: Why does Postsyn reject the user's pre-synthesis constraints on an FDC file when Reveal Inserter is included in the project?
Description: The issue is caused by some differences in the behavior of the Verific and Synplify language parsers related to the handling of the escape characters in the instance name. Solution: This is not yet fixed by Synplify Pro and no timeline ...788 - Synplify Pro Standalone: Why the Lattice version of Synplify Pro NOT ALLOW to run the Synplify.exe or Synplify_pro.exe programs from the command line?
Synplify Pro Standalone: The Lattice OEM licence of Synplify Pro does not support running the Synplify.exe or Synplify_pro.exe programs from the command line. You will need to use the Synpwrap.exe program instead. Below is a command line example of ...7713 - Radiant Synthesis with Synplify Pro: results differ on multiple machines
Description: When using Synplify Pro on different machines, the system environment could cause different behavior. Some symptoms of this issue include the following: 1. The synthesis behavior is different on another machine (e.g. passes or fails on a ...736 - Lattice ispLEVER: Synthesis: Synplify Pro: How do I use Synplify PRO to view a schematic representation of the RTL in my project?
Lattice ispLEVER: Synthesis: Synplify Pro: To view the schematic representation of the RTL in your project in ispLEVER, do the following: Do a BUILD DATABASE Select TOOLS, SYNPLIFY PRO SYNTHESIS Select HDL-Analyst Select RTL, HIERARCHICAL VIEW (or) ...