5173 - ispLEVER Classic: Where to find the reserved file name extensions?

• Related Articles

• 1193 - ispLEVER Classic / Installation: What to do if error pops out when starting ispLEVER Classic "Can't read the ini file."?

  Description: At start up, ispLEVER looks for an initialization file that is normally located under the lsc_env file (which normally sits directly under the C: drive). If ispLEVER cannot find this file (e.g. C:\lsc_env\lsc_1_4.ini), then the user will ...

• 1925 - ispLEVER Classic: "missing pin name" error

  Description: This error is because there is no name for the pin. Solution: Users need to provide names to the pins to solve this problem. To assign a name to pin Add a wire and then name the wire. Refer to the "Schematic Entry Reference Manual".

• 3590 - ispLEVER Classic v1.7: Where do I find the IPexpress in the software? <br>

  Solution: One can generate the IP using Module-IP Manager that comes along with the ispLEVER Classic 1.7 Installation. The Module-IP Manager can be invoked as follows. Select Windows > All Programs > Lattice ispLEVER Classic 1.7 > Module- IP Manager

• 757 - ispLEVER Classic: What does the "Information in file ispsys.ini does not match the system" error mean?

  Solution: The message that you are getting indicates that there is a mismatch between the registry settings and the ispLEVER "*.ini" file. e.g."lsc_1_3.ini" file (for ispLEVER Classic 1.3). The "ispsys.ini" file points to the "*.ini" file (e.g. ...

• 4347 - ispLEVER Classic v1.8: Does the software support&nbsp;Mixed Verilog/VHDL&nbsp;as described in the&nbsp;ispLEVER Classic Installation Guide?

  Solution: Classic does not support a mixed language project. Note that when you create a project, you have to choose a project type. Mixed language is not one of these. ispLEVER and Diamond do support mixed language but not Classic. The workaround is ...