Karl Hammar wrote:
+1 for nc since ICs have pins that are labeled that way. Would the DRC just
ignore it, or would the DRC complain if it was connected to anything?
+1
...
Since nc is just a piece of copper attached to the (plastic/ceramic)
package, why should drc complain?
A nc pin
Since nc is just a piece of copper attached to the (plastic/ceramic)
package, why should drc complain?
A nc pin would be like pas, but gives no error if unconnected.
The documentation of the Renesas TinyH8 states:
... Do not connect anything to the nc-pins. They might be used as test
I have seen this handled in other CAD packages not by making the pin
an NC in the symbol, but by having a feature in the schematic where
the pin can be No Connected so that it is not flagged as an error
if it has no wire.
Or course, it makes some sense to have a special type of NC in a
El mar, 28-09-2010 a las 15:36 +0200, Karl Hammar escribió:
Karl:
1b, identify the correct meaning of pintype values as used today
Since drc2 is the only user of the pintype value, I looked into it.
...
Note A,
since drc-matrix is symmetric (connection a - b is the
same as
John Doty:
On Sep 28, 2010, at 12:39 PM, Karl Hammar wrote:
In gnet-drc2.scm:
;; Example:
;; (define dont-check-non-numbered-parts 1)
...
and there is also descriptions how to alter what is allowed to
connect to what in the file. The problem seems to get that inside
gnetlist -g
Kai-Martin Knaak:
Karl Hammar wrote:
5, add a tutorial on how to adapt the DRC rules to the local needs
Well documented examples would take me a long way.
Ok, I'll use http://turkos/git/openhw/wascator_c240/styrkort.sch as an
example.
*
How to tell drc2 which tests to skip:
$
Kai-Martin Knaak:
Karl Hammar wrote:
4, add explicit documentation on the rules in the wiki
I'm not the wiki man. I could read the code (I assume you mean drc2)
and try to describe it in text, but someone else has to enter it
into the wiki.
Ok, if you describe the rules here on the
Kai-Martin Knaak:
Karl Hammar wrote:
...
6, add some kind of GUI control to activate/deactivate rules
Gui things are for others to contribute with, but maybe if we could
make drc2 react on some attributes?
How about an attribute to the connecting net to silence drc2 at this
specific
Kai-Martin Knaak:
Karl Hammar wrote:
Shall we update the distributed sym files so they pass gsymcheck ?
Yes, please.
..
Should a missing numslots=0 really be a warning?
...
ack. It has been quite some time that numslots=0 is not necessary
anymore.
Ok, a first step would then be:
1,
Karl:
Kai-Martin Knaak:
Karl Hammar wrote:
Shall we update the distributed sym files so they pass gsymcheck ?
Yes, please.
..
Should a missing numslots=0 really be a warning?
...
ack. It has been quite some time that numslots=0 is not necessary
anymore.
Ok, a first step would
-Original Message-
Karl Hammar wrote
Ok, a first step would then be:
1, add/correct pintype to the sym files
1a, which programs use pintype
1b, identify the correct meaning of pintype values as used today
1c, add missing pintypes (eg. should we have one for nc)
2, remove
Kai-Martin Knaak:
Karl Hammar wrote:
Shall we update the distributed sym files so they pass gsymcheck ?
Yes, please.
..
Should a missing numslots=0 really be a warning?
...
ack. It has been quite some time that numslots=0 is not necessary
anymore.
Ok, a first step would then
Andrew Miner:
Karl Hammar wrote
...
1c, add missing pintypes (eg. should we have one for nc)
...
+1 for nc since ICs have pins that are labeled that way. Would the DRC just
ignore it, or would the DRC complain if it was connected to anything?
...
Since nc is just a piece of copper
Karl:
1b, identify the correct meaning of pintype values as used today
Since drc2 is the only user of the pintype value, I looked into it.
...
Note A,
since drc-matrix is symmetric (connection a - b is the
same as connection b - a) and it is not directly referenced by
anything else
Karl Hammar wrote:
1, add/correct pintype to the sym files
1a, which programs use pintype
1b, identify the correct meaning of pintype values as used today
1c, add missing pintypes (eg. should we have one for nc)
2, remove numslots=0 warning from gsymcheck
Anything else?
3, remove
On Sep 28, 2010, at 12:39 PM, Karl Hammar wrote:
In gnet-drc2.scm:
;; Example:
;; (define dont-check-non-numbered-parts 1)
;; (define dont-check-duplicated-references 1)
;; (define dont-check-one-connection-nets 1)
;; (define dont-report-unknown-pintypes 1)
;; (define
Kai-Martin Knaak:
Karl Hammar wrote:
...
Should a missing numslots=0 really be a warning?
ack. It has been quite some time that numslots=0 is not necessary
anymore.
...
2, remove numslots=0 warning from gsymcheck
Attached patch does that.
Regards,
/Karl Hammar
-
Aspö Data
On Sep 28, 2010, at 6:00 AM, Andrew Miner wrote:
would also like to see a pwr_src pin type which would be the output of the
voltage regulator (or source). That way the DRC would warn you if you
shorted two power sources together or if you forgot to hook one of your
power input pins to the
On Sep 28, 2010, at 6:32 AM, Karl Hammar wrote:
Since nc is just a piece of copper attached to the (plastic/ceramic)
package, why should drc complain?
A nc pin would be like pas, but gives no error if unconnected.
This is not a true statement, some packages there are Do not connect, some
On Sep 28, 2010, at 12:59 PM, Steven Michalske smichal...@gmail.com wrote:
On Sep 28, 2010, at 6:00 AM, Andrew Miner wrote:
would also like to see a pwr_src pin type which would be the output of the
voltage regulator (or source). That way the DRC would warn you if you
shorted two power
On Sep 28, 2010, at 2:30 PM, Edward Hennessy wrote:
Side note:
A capabilities attribute that might get a string like
'Current_RMS_supply=1A; current_peak_supply=1...@0.5s'
It would be nice to have an attribute to check if a power pin is connected to
the proper supply voltage.
The
Karl Hammar wrote:
4, add explicit documentation on the rules in the wiki
I'm not the wiki man. I could read the code (I assume you mean drc2)
and try to describe it in text, but someone else has to enter it
into the wiki.
Ok, if you describe the rules here on the list, I'd volunteer to
Karl Hammar wrote:
That way the DRC would warn you if you
shorted two power sources together or if you forgot to hook one of
your
power input pins to the power plane (and only connected it to a
capacitor
instead).
+1
+1
Just today I had a student stumble on an accidental connection of
Shall we update the distributed sym files so they pass gsymcheck ?
Should gsymcheck really complain about a missing numslots=0
and report error for a net=GND:2 attribute?
***
When doing pcb import schematic, I get the message:
Remember to check that your schematic has no errors using the drc2
On Sep 26, 2010, at 2:31 AM, Karl Hammar wrote:
The U3 is the lm7805-1.sym from gschem and it does not contain any
pintype attribute.
It is easy enought to correct:
$ diff `locate lm7805-1.sym`
1c1
v 20080127 1
---
v 20031231 1
19,20d18
T 300 600 5 10 0 0 0 0 1
Karl Hammar wrote:
Shall we update the distributed sym files so they pass gsymcheck ?
Yes, please.
I gave up on gsymcheck because it caused more work due to false alarms
than it saved by pointing to real errors.
Should a missing numslots=0 really be a warning?
It is annoying to include it
26 matches
Mail list logo
