7688 - [All Nexus] Why Lattice Radiant tool shows Error <71241012> The clock port [clock_name] is assigned to a non-clock pin ?

• Related Articles

• 3642 - Diamond: Why does the following warning message appear in Spreadsheet View of the software when a single-ended clock pin in the design is assigned to a Primary Clock port?

  Description: WARNING - Warning -The clock port [RCLK] is assigned to a non clock dedicated pin [D14], which might affect the clock performance. Solution: In the Spreadsheet View of Lattice Diamond Software, if the clock pin is assigned to a ...

• 6850 - Diamond: ERROR - Based on the current IO attributes settings, port xxxxx cannot be assigned to pin [xx].

  Description: This article explains an error in Diamond which reports the port cannot be assigned to certain pin during synthesis due to the pin assignment done via constraint. Solution: This error in Diamond is caused by optimization done during ...

• 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".

• Lattice Radiant: What does this warning mean&nbsp;<b><i>"Generated_clock: not connect to any master clock pin."</i></b>?

  Description: The user encounters a WARNING message shown below whenever they utilize a PLL IP. "Generated_clock: not connect to any master clock pin." Solution: The warning implies that the timing engine is indicating that there is no clock at the ...

• 6982 - Radiant: Why do we encounter the error: "PAR does not support signal <clock name> driving more than two DCCs"?

  Solution: In Lattice Radiant software, the error "PAR does not support signal driving more than two DCC" is because PAR (Place and Route) only supports one or two DCC (Dynamic Clock Control) loads for one clock signal at present. The reason is, each ...