Constraint Port Without Pin in Configuration

This compiler hint relates to the constraint file dealing with port-to-connector mappings for a Peripheral Board. It appears when the record for a port specifies connection to an invalid pin (one that does not exist on the Peripheral Board's connector). The message is displayed in the Messages panel in the following format:

Configuration ConfigurationName has port in constraint file without any pin mapped: PortName,

where

ConfigurationName is the name of the configuration to which the offending port's parent constraint file is associated.

PortName is the name of the offending port.

Default Report Mode

Warning

Recommendation

Use the Compile Errors dialog to quickly cross probe to the constraint file containing the problematic port definition. Locate the constraint record for the port - the PortName entry in the violation message corresponds to the assigned value for the record's TargetId field. Where the connection has been explicitly defined, the value entered for the record's ConnectTo field must be in the form:

ConnectorName-PinNumber,

where

ConnectorName must be the same name as that entered when declaring the connector. The record declaring the connector will be located previously within the same constraint file and appears in the form:

Record=Constraint | TargetKind=Connector | TargetId=ConnectorName

PinNumber must be a valid (existing) pin on the connector.

Change the ConnectorName prefix and/or the PinNumber, as required, to satisfy these conditions.