docs/wiki/geda_faq-gnetlist.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"
   4  lang="en" dir="ltr">
   5 <head>
   6   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   7   <title>geda:faq-gnetlist</title>
   8 <meta name="generator" content="DokuWiki Release rc2007-05-24" />
   9 <meta name="robots" content="index,follow" />
  10 <meta name="date" content="2007-05-24T22:27:26-0400" />
  11 <meta name="keywords" content="geda,faq-gnetlist" />
  12 <link rel="search" type="application/opensearchdescription+xml" href="http://geda.seul.org/wiki/lib/exe/opensearch.php" title="geda Wiki" />
  13 <link rel="start" href="http://geda.seul.org/wiki/" />
  14 <link rel="contents" href="http://geda.seul.org/wiki/geda:faq-gnetlist?do=index" title="Index" />
  15 <link rel="alternate" type="application/rss+xml" title="Recent Changes" href="http://geda.seul.org/wiki/feed.php" />
  16 <link rel="alternate" type="application/rss+xml" title="Current Namespace" href="http://geda.seul.org/wiki/feed.php?mode=list&ns=geda" />
  17 <link rel="alternate" type="text/html" title="Plain HTML" href="http://geda.seul.org/wiki/_export/xhtml/geda:faq-gnetlist" />
  18 <link rel="alternate" type="text/plain" title="Wiki Markup" href="http://geda.seul.org/wiki/_export/raw/geda:faq-gnetlist" />
  19 <link rel="stylesheet" media="all" type="text/css" href="lib/exe/css" />
  20 <link rel="stylesheet" media="screen" type="text/css" href="lib/exe/001css" />
  21 <link rel="stylesheet" media="print" type="text/css" href="lib/exe/002css" />
  22 </head>
  23 <body>
  24 <div class="dokuwiki export">
  25 <div class="toc">
  26 <div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
  27 <div id="toc__inside">
  28
  29 <ul class="toc">
  30 <li class="level1"><div class="li"><span class="li"><a href="#gnetlist_build_run-time_problems" class="toc">Gnetlist build/run-time problems</a></span></div>
  31 <ul class="toc">
  32 <li class="level2"><div class="li"><span class="li"><a href="#i_get_a_parenthesis_mismatch_error_when_running_gnetlist._what_s_up" class="toc">I get a &quot;parenthesis mismatch&quot; error when running gnetlist.  What&#039;s up?</a></span></div></li>
  33 <li class="level2"><div class="li"><span class="li"><a href="#the_gnetlist_bom_backend_does_not_work._what_is_wrong" class="toc">The gnetlist bom backend does not work. What is wrong?</a></span></div></li>
  34 <li class="level2"><div class="li"><span class="li"><a href="#some_gnetlist_backends_overflow_the_stack._how_do_i_solve_this" class="toc">Some gnetlist backends overflow the stack. How do I solve this?</a></span></div></li>
  35 <li class="level2"><div class="li"><span class="li"><a href="#gnetlist_has_created_a_netlist_with_duplicate_pins" class="toc">gnetlist has created a netlist with duplicate pins!?</a></span></div></li></ul>
  36 </li></ul>
  37 </div>
  38 </div>
  39
  40
  41
  42 <h1><a name="gnetlist_build_run-time_problems" id="gnetlist_build_run-time_problems">Gnetlist build/run-time problems</a></h1>
  43 <div class="level1">
  44
  45 </div>
  46 <!-- SECTION "Gnetlist build/run-time problems" [1-48] -->
  47 <h2><a name="i_get_a_parenthesis_mismatch_error_when_running_gnetlist._what_s_up" id="i_get_a_parenthesis_mismatch_error_when_running_gnetlist._what_s_up">I get a &quot;parenthesis mismatch&quot; error when running gnetlist.  What&#039;s up?</a></h2>
  48 <div class="level2">
  49
  50 <p>
  51  Starting with Fedorea Core 6 and SuSE 10.2, many users have reported an error which looks like this:
  52 </p>
  53 <pre class="code">
  54 $gnetlist -g spice-sdb -o TwoStageAmp.cir TwoStageAmp.sch
  55 Command line passed = gnetlist -g spice-sdb -o TwoStageAmp.cir TwoStageAmp.sch
  56 gEDA/gnetlist version 20061020
  57 gEDA/gnetlist comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
  58 This is free software, and you are welcome to redistribute it under certain
  59 conditions; please see the COPYING file for more details.
  60
  61 Remember to check that your schematic has no errors using the drc2 backend.
  62 You can do it running &#039;gnetlist -g drc2 your_schematic.sch -o drc_output.txt&#039;
  63 and seeing the contents of the file drc_output.txt.
  64
  65 Loading schematic [/home/nano/TwoStageAmp/TwoStageAmp.sch]
  66 Probably parenthesis mismatch in /usr/share/gEDA/scheme/gnet-spice-sdb.scm
  67 Most recently read form: (#@begin #&lt;unspecified&gt;)
  68 ERROR: Unbound variable: spice-sdb
  69 </pre>
  70
  71 <p>
  72 Several gnetlist backends evince this problem, including spice-sdb and drc2.
  73 </p>
  74
  75 <p>
  76 This is a bug in guile-1.8.X.  The gEDA developers are working on a fix.  Meanwhile, try to backrev your version of guile to 1.6.7, which is known to work flawlessly with gEDA.
  77 </p>
  78
  79 </div>
  80 <!-- SECTION "I get a parenthesis mismatch error when running gnetlist.  What's up?" [49-1315] -->
  81 <h2><a name="the_gnetlist_bom_backend_does_not_work._what_is_wrong" id="the_gnetlist_bom_backend_does_not_work._what_is_wrong">The gnetlist bom backend does not work. What is wrong?</a></h2>
  82 <div class="level2">
  83
  84 <p>
  85 If when running gnetlist like this:
  86 </p>
  87 <pre class="code">gnetlist -g bom filename.sch</pre>
  88
  89 <p>
  90 and gnetlist outputs an error message like:
  91 </p>
  92 <pre class="code">Loading schematic [filename.sch]
  93 ERROR: In procedure open-file:
  94 ERROR: No such file or directory: “attribs”</pre>
  95
  96 <p>
  97 then you need to create a file called “attribs” in the current directory which contains the attributes which you want inside the bom file. An example of this file would be: <pre STYLE="background : Lightgreen;margin-left : 2em"><font size="+0">refdes
  98 device
  99 value</font></pre>
 100 </p>
 101
 102 </div>
 103 <!-- SECTION "The gnetlist bom backend does not work. What is wrong?" [1316-1844] -->
 104 <h2><a name="some_gnetlist_backends_overflow_the_stack._how_do_i_solve_this" id="some_gnetlist_backends_overflow_the_stack._how_do_i_solve_this">Some gnetlist backends overflow the stack. How do I solve this?</a></h2>
 105 <div class="level2">
 106
 107 <p>
 108 If you get an error message like:
 109 </p>
 110 <pre class="code">ERROR: Stack overflow</pre>
 111
 112 <p>
 113 when running certain larger sized schematics through some of the backends, then add the following to a <strong><code>~/.gEDA/gnetlistrc</code></strong> or a local <strong><code>gnetlistrc</code></strong> (in the current working directory):
 114 </p>
 115 <pre class="code">(debug-options (list &#039;stack 200000))
 116 (eval-options (list &#039;stack 200000))</pre>
 117
 118 <p>
 119 If this does not work, then edit the appropriate backend (usually named: gnet-backend_name.scm) and put the above lines at the top of this file. The gnetlist backends can be found in <strong><code>${prefix}/share/gEDA/scheme</code></strong>. Also send an e-mail to geda-dev reminding the developers to fix this. Remember, you must subscribe to geda-dev before you post to the geda-dev e-mail list.
 120 </p>
 121
 122 </div>
 123 <!-- SECTION "Some gnetlist backends overflow the stack. How do I solve this?" [1845-2650] -->
 124 <h2><a name="gnetlist_has_created_a_netlist_with_duplicate_pins" id="gnetlist_has_created_a_netlist_with_duplicate_pins">gnetlist has created a netlist with duplicate pins!?</a></h2>
 125 <div class="level2">
 126
 127 <p>
 128 There has been at least one report of the following message coming from PCB after loading up a netlist created by gnetlist:
 129 </p>
 130 <pre class="code">28: Error! Element R117 pin 2 appears multiple times in the netlist file.
 131 29: Error! Element C167 pin 2 appears multiple times in the netlist file.</pre>
 132
 133 <p>
 134 What has happened is gnetlist (really libgeda) created two nets instead of one. This happens when you draw two nets that cross each other and a pin connecting to the intersection of the two crossing nets. Note the cross nets are not connected together. A schematic which demonstrates this looks like this:
 135 </p>
 136
 137 <p>
 138 <a href="_detail/geda_ambiguous1.html" class="media" title="geda:ambiguous1.png"><img src="_media/geda_ambiguous1.png" class="media" alt="" /></a>
 139 </p>
 140
 141 <p>
 142 The developers are debating whether or not this is a bug in gnetlist, but for now make sure your net connections, especially those that involve pins connecting to the middle of other nets, are explicitly drawn. Here is how the above connection should be drawn to netlist properly:
 143 </p>
 144
 145 <p>
 146 <a href="_detail/geda_ambiguous1_fixed.html" class="media" title="geda:ambiguous1_fixed.png"><img src="_media/geda_ambiguous1_fixed.png" class="media" alt="" /></a>
 147 </p>
 148
 149 </div>
 150 <!-- SECTION "gnetlist has created a netlist with duplicate pins!?" [2651-] --></div>
 151 </body>
 152 </html>