| Author |
Message |
McMurry
Joined: 16 Feb 2008
Posts: 75
|
 29 Mar 2008 18:59 warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
I often get annoying warning of output pins stuck at gnd or vcc. I know it means no harm, but is there any other coding method that I could get rid of them?
Last edited by McMurry on 30 Mar 2008 4:24; edited 1 time in total |
|
| Back to top |
|
 |
Google
AdSense
|
29 Mar 2008 18:59 Ads |
|
|
|
|
|
|
| Back to top |
|
|
FvM
Joined: 22 Jan 2008
Posts: 5154
Helped: 766
Location: Bochum, Germany
|
29 Mar 2008 21:14 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
| No, some pins are actually hardwired to VCC or GND. The warning wants to assure, that you didn't unintentionally forget to drive a pin. With most HDL tools, warnings can selectively be disabled.
|
|
| Back to top |
|
|
McMurry
Joined: 16 Feb 2008
Posts: 75
|
30 Mar 2008 2:28 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
| I am using qu(at)rtus II. How can it be disabled?
|
|
| Back to top |
|
|
FvM
Joined: 22 Jan 2008
Posts: 5154
Helped: 766
Location: Bochum, Germany
|
30 Mar 2008 9:42 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
| Quote: |
To enable or disable specific HDL messages in your HDL, use the message_on and message_off synthesis directives. Both directives take a space-separated list of Message IDs. You can enable or disable messages with these synthesis directives immediately before Verilog HDL modules, VHDL entities, or VHDL architectures. You cannot enable or disable a message in the middle of an HDL construct.
A message enabled or disabled via a message_on or message_off synthesis directive overrides its HDL Message Level or any message_level synthesis directive. The message will remain disabled until the end of the source file or until its status is changed by another message_on or message_off directive. |
// altera message_off 10000
-- altera message_off 10000
|
|
| Back to top |
|
|
McMurry
Joined: 16 Feb 2008
Posts: 75
|
30 Mar 2008 13:28 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
| FvM wrote: |
// @ltera message_off 10000
-- @ltera message_off 10000 |
thanks, but i think it doesnt work with qu(at)rtus II. keep getting error, instead of just warnings.
|
|
| Back to top |
|
|
robinh
Joined: 18 Jan 2002
Posts: 61
Helped: 1
|
30 Mar 2008 14:46 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
In my point of vue, if you get warnings about ouputs stuck at gnd or vcc, it might reflect the fact that your design generates always zero or one on the corresponding pins.
The warning is here to make you verify if you do not have any misconception in your design (vhdl or schematic), that conducts to this situation.
|
|
| Back to top |
|
|
FvM
Joined: 22 Jan 2008
Posts: 5154
Helped: 766
Location: Bochum, Germany
|
30 Mar 2008 15:49 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
| Quote: |
| but i think it doesnt work with qu(at)rtus II. keep getting error, instead of just warnings. |
A unknown synthesis option shouldn't give an error, it's just a comment. I suggest, that you read the quoted instructions in qu(at)rtus II manual yourself and use the suitable synthesis options. I posted Verilog and VHDL version together, assuming you would use what fits your design. Also the 10000 has to be replaced with the warning number that you want to suppress.
However, I'm not absolutely sure, if "pin stuck to xx" warnings can be disabled this way, but I assume, that this works when the said synthesis option is placed in the top design file. Alternatively, warnings can be disabled in the qu(at)rtus GUI, the method is explained in the same qu(at)rtus manual chapter.
Added after 19 minutes:
It turns out, that the "stuck pin" warning can't be supressed, cause the ID 13401 isn't in the range of regular synthesis warning IDs, although the warning is issued during Analysis & Synthesis phase. So apparently, the warnings can't be suppressed. Strange indeed.
|
|
| Back to top |
|
|
McMurry
Joined: 16 Feb 2008
Posts: 75
|
30 Mar 2008 18:45 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
ooh...
thanks for the information =)
Added after 12 minutes:
| robinh wrote: |
In my point of vue, if you get warnings about ouputs stuck at gnd or vcc, it might reflect the fact that your design generates always zero or one on the corresponding pins.
The warning is here to make you verify if you do not have any misconception in your design (vhdl or schematic), that conducts to this situation. |
yup. that's the case =)
just those warning are quite annoying.
probably there is another method of coding that would omit such warning? 
i'm using something like 11100000 WHEN '0' ELSE 10101111... hmmm..
|
|
| Back to top |
|
|
j_andr
Joined: 30 Mar 2008
Posts: 107
Helped: 20
Location: europe
|
30 Mar 2008 23:44 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
| McMurry wrote: |
I often get annoying warning of output pins stuck at gnd or vcc.
I know it means no harm, but is there any other coding method that I could get rid of them? |
I think you are wrong;
it usually means you did something wrong if your
output stuck vcc/gnd;
I'd never try to filter out such warnings;
J.A
|
|
| Back to top |
|
|
FvM
Joined: 22 Jan 2008
Posts: 5154
Helped: 766
Location: Bochum, Germany
|
31 Mar 2008 0:02 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
| Quote: |
| it usually means you did something wrong if your output stuck vcc/gnd |
Not necssary. In some cases, you have e. g. a chip enable, that is permantly active in a design. Then you get the warning. With qu(at)rtus, there are exactly two warnings for outputs:
1. A synthesis tool warning, when an output is set to a constant level from HDL code. The discussed "11100000" WHEN '0' ELSE "10101111" would e. g. issue this warning for several bits.
2. A fitter warning issued for any defined output pin, that has a constant level either set in HDL code or by default cause the pin isn't driven at all.
I generally agree, that the warning has the important purpose to reveal inactive resources in the design, together with other warnings for registers without clock or inputs not driving logic, it can help to find design errors.
|
|
| Back to top |
|
|
j_andr
Joined: 30 Mar 2008
Posts: 107
Helped: 20
Location: europe
|
31 Mar 2008 0:13 Re: warning of output pins stuck at gnd or vcc (CPLD) |
|
|
|
|
| FvM wrote: |
| Not necssary/.../ |
right, that's why I said 'usually', not 'always'  ;
how many times fpga pins are used to drive stable logic level 1/0 - 1% ?
these devices are slightly too expensive to use them as a connection
to gnd or vcc ;
so my advice - never filter out this warnig because you can mask out
a hint of a serious error in your rtl code;
J.A
|
|
| Back to top |
|
|
