7264 - Diamond / Radiant / Propel: long startup time, stuck at "initializing device data"
Description:
When launching Lattice software, some license checks will be performed that may take some time depending on the user's system configuration. This FAQ summarizes the work arounds to shorten the startup time.
Solution:
1) Checking the environment variables
Under the Environment Variables, please check the LM_LICENSE_FILE and LATTICE_LICENSE_FILE variables:
- Make sure that only valid paths are stored in the variable. The existence of unused paths can slow down the loading time of the software tool.
- Place the path of the Lattice Radiant and Diamond license to the top to prevent the tool from looking at other paths.
Under the Environment Variables, please check the LM_LICENSE_FILE and LATTICE_LICENSE_FILE variables:
- Make sure that only valid paths are stored in the variable. The existence of unused paths can slow down the loading time of the software tool.
- Place the path of the Lattice Radiant and Diamond license to the top to prevent the tool from looking at other paths.
- Also check for any possible contentions for both the System and User variables. For example, having different values set in the user and system variables
2) Checking the Registry Editor
Open the Registry Editor
2) Checking the Registry Editor
Open the Registry Editor
Select the top registry and search for LM_LICENSE_FILE and LATTICE_LICENSE_FILE.
If there are multiple locations in the variable, click it and right-click > Modify...
Make sure that the registry value is only the path pointing to the Lattice license file.
After doing this Ctrl+F and continue to search the registries until there are no more hits.
Restart your PC and try starting the software again.
3) Setting a new environment variable
If the issue persists after the workarounds above and te license being used is a FLOATING license, please try the following:
a. Try setting a new environment variable: FLEXLM_NO_CKOUT_INSTALL_LIC with value 1.
b. This will prevent the license from automatically updating LATTICE_LICENSE_FILE after a successful license checkout.
c. Here is an example:
Related Articles
6459 - Radiant and Diamond: How to resolve the long delay of launching the software and getting stuck at "initializing device data"?
Please try below solutions: Try to retain all valid values only in the LM_LICENSE_FILE environment variable and delete any paths in the variable that are pointing to a port@servername or any file path that is no longer available or existing. The ...7733 - ECP5 / Diamond 3.14: Why does my design get a Map device oversize error related to PLL for LFE5U-12F in with Diamond 3.14, but completes map successfully in earlier releases of Diamond software?
In Diamond version 3.14, there is a bug where it incorrectly limits the number of PLLs in the device to 0 for LFE5U-12F. Example error message: ERROR - (device oversize error). The number of PLL components needed (1) exceeds the number available. ...7262 - Radiant and Diamond: HDL pin constraints not seen in Spreadsheet View/Device Constraint Editor
Description: In Lattice Radiant and Diamond, while using the Spreadsheet View/Device Constraint Editor, it is possible to not see the HDL pin constraints reflected in GUI. Solution: This may be because the pins mentioned in the lines of code have ...3719 - Programmer: How do we know the expected Device ID of the FPGA using the Diamond or Radiant Programmer?
In the Diamond or Radiant Programmer window, from the View menu -> select Columns -> select Device ID This will enable the Device ID column in the main Programmer window. Example: Diamond Programmer Example: Radiant Programmer6477 - Radiant and Diamond: It is acceptable to use an industrial-grade bitstream to a commercial-grade device?
It is acceptable to use an industrial-grade bitstream in a commercial-grade device as long as it remains within the temperature range of the commercial-grade device.