Re: gEDA-user: making gnetlist calm down
Hi, thanks for your answer. Ales Hvezda [EMAIL PROTECTED] writes: [snip] Found duplicate net name, renaming [+3.3V] to [BS1] WARNING: Trying to rename something twice: +3.3V and +3.3V are both a src and dest name This warning is okay if you have multiple levels of hierarchy! This warning shows up when you have named a net twice, usually once with netname= and then again by attaching a power symbol. If this is okay to you, then you can ignore these messages. Keep in mind that gnetlist will pick one of the net names and run with it. If it isn't the one you wanted, then you need to change your schematic (to only name a net once). That makes sense. I guess, this naming change is coherent for all the schematics prosessed in one run, and won't rip nets apart? Than that's really not a problem. regards, David -- GnuPG public key: http://user.cs.tu-berlin.de/~dvdkhlng/dk.gpg Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: making gnetlist calm down
This is my first complex design and I have three annoying problems: problem 1: There are lots of floating pins in the design. Is there some way to explicitly tell gnetlist that a pin is intentionally left floating? problem 2: I get several errors like this: ERROR: Pin(s) with pintype 'unknown': U47:10 U48:10 U49:10 U50:10 U45:10 [snip] are connected to pin(s) with pintype 'unknown': U47:10 U48:10 U49:10 U50:10 U45:10 [snip] These ICs referenced are ones included in the gEDA distribution. I'm using version 20060907 as installed from the ISO image. problem3: ERROR: Net unnamed_net58 is not driven. How do I figure out where unnamed_net58 actually is? -- David Griffith [EMAIL PROTECTED] A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: making gnetlist calm down
problem 2: I get several errors like this: ERROR: Pin(s) with pintype 'unknown': U47:10 U48:10 U49:10 U50:10 U45:10 [snip] are connected to pin(s) with pintype 'unknown': U47:10 U48:10 U49:10 U50:10 U45:10 [snip] If you look in the gschem master attributes list it tells you what the pintype is for. It can be (is?) used for design rule checking. Many symbols haven't got these attributes defined, which causes the warning. I ignore these. problem3: ERROR: Net unnamed_net58 is not driven. How do I figure out where unnamed_net58 actually is? If gnetlist generates a netlist file you can maybe look for unnamed_net58 in there and see what it's connected to (presumably just one thing). ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: making gnetlist calm down
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi David problem 1: There are lots of floating pins in the design. Is there some way to explicitly tell gnetlist that a pin is intentionally left floating? There is a nc (not connected) symbol in the library. If you connect a floating pin to it gnetlist won't display the warning. I personally don't like to use it because I think it clutters up the schematics. Best regards Tomaz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFeTc/sAlAlRhL9q8RAq+iAJ99OT1HAsQguodBjZZHNr+K0wC3wACfap/d +Aytx1Pa7sHYJ79I4MGFYhg= =vr1W -END PGP SIGNATURE- ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: making gnetlist calm down
Hi, David Griffith [EMAIL PROTECTED] writes: This is my first complex design and I have three annoying problems: [..] good coincidence and a good chance to add my problems to the list :) I'm currently also just in the process of netlisting a complex design in preparation for PCB layouting. I also get some output from gnetlist that seems to point to severe errors, although I don't understand it at all: $gnetlist -g drc2 -o ZA100_drc.txt ZA100_1.sch ZA100_2.sch ZA100_3.sch [..] Found duplicate net name, renaming [+3.3V] to [BS1] WARNING: Trying to rename something twice: +3.3V and +3.3V are both a src and dest name This warning is okay if you have multiple levels of hierarchy! Found duplicate net name, renaming [PGND] to [R/W#] Found duplicate net name, renaming [R/W#] to [RD#] WARNING: Trying to rename something twice: PGND and PGND are both a src and dest name This warning is okay if you have multiple levels of hierarchy! WARNING: Trying to rename something twice: PGND and PGND Can I really ignore such errors, or is this going to be a problem when moving on with gsch2pcb? BTW I'm using quite recent geda-gnetlist-20060906 (but the problem was present with a much older version, too) regards, David Kühling -- GnuPG public key: http://user.cs.tu-berlin.de/~dvdkhlng/dk.gpg Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
