Answers Database
SYNTHX 5.0: Possible cause of 'pin was not defined', design worked in last rev
Record #386
Problem Title:
SYNTHX 5.0: Possible cause of 'pin was not defined', design worked in last rev
Problem Description:
Solution 1:
Check Customer Design to ensure that:
1- The pin that the Synthx is complaining about has been defined and used in the design.
2- Also, check the other signals that are used in conjunction with the pin that is the cause of the
warning. For example,
*** SYNTHX: WARNING:
The external module signal "temp" pin was defined but not used in your design.
if temp is used in
output = (undefinedPIN $ temp);
then although temp might be defined and used legally, it might give out a warning. This is because
the other pin (undefinedPIN) might not be declared properly, and the compiler will assign a specific
value to it. In that case, pin "temp"s state no longer has an affect on the signal "output" and thus
is ignored.
Solution 2:
SYNTHX 5.0 may produce a warning similar to the following on some designs:
*** SYNTHX: WARNING:
The external module signal DATA_STATE(example) pin was defined but not
used in your design.
In some cases, there may actually be a problem with the design file. However,
if the design file looks valid, try changing the name of the function. It
appears that functions containing the word "state" may cause SYNTHX to
issue warning messages.
End of Record #386 - Last Modified: 04/07/99 16:44 |
