kai-martin knaak wrote:
Karl Hammar wrote:
Running gnetlist -g drc2 on a schematic I get:
input/output -- pwr
input and output are meant to refer to signals. The DRC assumes that
signals should never be connected to power lines. With analog circuits
there is no strict
Tying a digital input directly to a power rail is a bit like doing a
crossword puzzle in ink. You need a lot of confidence to do that in
a real design. I typically use a resistor to pull them up or
down. That can always be hacked, power connections can be hard to
access to modify them.
Hi Karl,
El dom, 26-09-2010 a las 11:33 +0200, Karl Hammar escribió:
[snip]
Checking pins without the 'pintype' attribute...
Checking type of pins connected to a net...
WARNING: Pin(s) with pintype 'output': U2:9
are connected by net 'unnamed_net61'
to pin(s) with pintype
kai-martin knaak wrote:
The unconnected pins can be left unconnected, how can I make it
accept that?
I don't know. I put my own nc.sym at pins that are deliberately not
connected. This symbol contains just one pin and no net. However,
DRC still complains, because the generated net is
Running gnetlist -g drc2 on a schematic I get:
Checking non-numbered parts...
Checking duplicated references...
Checking nets with only one connection...
Checking pins without the 'pintype' attribute...
Checking type of pins connected to a net...
WARNING: Pin(s) with pintype 'output': U2:9
Karl Hammar wrote:
Running gnetlist -g drc2 on a schematic I get:
(...)
Why does it warn about
output -- input/output
Don't know. IMHO, this combination should be fine.
input/output -- pwr
input and output are meant to refer to signals. The DRC assumes that
signals should never
6 matches
Mail list logo
