Quartus

Pin <name> drives global clock, but is not placed in a dedicated clock pin position


CAUSE: The specified pin drives the global clock, but is not placed in a dedicated clock pin position. This condition may be due to location or custom region assignments, the pin may be a bidirectional pin, or the pin may have registers. As a result, the tCO time may increase.
ACTION: Change the location or custom region assignments, or modify the design to change the pin to an input pin that does not have any registers.

See also:

Assigning an Entity or Node to a Custom Region
Assigning an Entity or Node to a Location
Changing Assignments
Overview: Making Assignments
Overview: Working with Assignments in the Floorplan Editor
Overview: Using Custom Regions

- PLDWorld -

 

Created by chm2web html help conversion utility.