5751 - Radiant 1.0 Service Pack 1: Why is there a fatal error when running PAR with the reference design named "Key Phrase Detection Using Compact CNN"?
Solution:
This is a known issue in Radiant 1.0 Service Pack 1 and is documented in FPGA-RD-02033 page 4 section 3 Software Requirements.
Related Articles
7739 - Radiant 2024.2 SP1: How can I resolve the PAR internal fatal error that only occurs on my design using Radiant 2024.2 SP1?
Description: In Radiant 2024.2 SP1, there is PAR internal fatal error occurs due to a crash on the STA. This error is not limited to a specific device. A symptom that the design is affected by this issue is if this design is passing PAR on older ...6664 - Radiant 2022.1 and below: Error: "ModuleNotFoundError: No module named 'secrets'"
Description: When using Radiant 2022.1 and below version to invoke "ipgen" TCL command for IP generation, below error might occur: "ERROR:root:code for hash md5 was not found. Traceback (most recent call last): File "bit_generator.pyx", line 40, in ...1242 - Simulation: Modelsim: What does "Fatal : Obsolete library format for design unit" Modelsim error mean?
Simulation: Modelsim: If the simulation libraries or your design files are compiled with an older version of Modelsim (for example, Modelsim 6.3) and are now being loaded (VSIM) into a newer version of Modelsim (for example, Modelsim 6.5), you will ...1915 - Diamond: ERROR - par: Failed to dump design to file.
The complete message for this error message is: ERROR - par: Failed to dump design to file <<FILE_PATH>/<FILE_NAME>.ncd> INTERNAL CODE : ncdesign:basncdesign:2244:2.13 In Diamond, when user performs PAR they might encounter this error message for ...111 - ModelSim: Fatal: vsim-3381 Obsolete library format for design unit.
Description: Fatal errors may be encountered when a design is loaded in Modelsim (VSIM). Designs using pre-compiled Lattice device models like the Physical Coding Sublayer logic, like the PCSD in the LatticeECP3 FPGA, are compiled for a specific ...