<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title></title> <link rel="stylesheet" media="screen" type="text/css" href="./style.css" /> <link rel="stylesheet" media="screen" type="text/css" href="./design.css" /> <link rel="stylesheet" media="print" type="text/css" href="./print.css" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> </head> <body> <h1 class="sectionedit2041"><a name="forward_backward_annotation_between_geda_gaf_and_pads_powerpcb" id="forward_backward_annotation_between_geda_gaf_and_pads_powerpcb">Forward/Backward Annotation Between gEDA/gaf and PADS PowerPCB</a></h1> <div class="level1"> <p> by: Dan McMahill </p> <p> This document is released under <a href="http://www.gnu.org/copyleft/fdl.html" class="urlextern" title="http://www.gnu.org/copyleft/fdl.html" rel="nofollow">GFDL</a> </p> <p> March 6th, 2003 </p> </div> <!-- EDIT2041 SECTION "Forward/Backward Annotation Between gEDA/gaf and PADS PowerPCB" [1-191] --> <h2 class="sectionedit2042"><a name="forward_annotation_of_geda_schematic_changes_to_pads_powerpcb_layout" id="forward_annotation_of_geda_schematic_changes_to_pads_powerpcb_layout">Forward Annotation of gEDA Schematic Changes to PADS PowerPCB Layout</a></h2> <div class="level2"> </div> <!-- EDIT2042 SECTION "Forward Annotation of gEDA Schematic Changes to PADS PowerPCB Layout" [192-272] --> <h2 class="sectionedit2043"><a name="overview" id="overview">Overview</a></h2> <div class="level2"> <p> Forward annotation is the process of updating a layout to reflect changes made in the schematic. This process is used when, for example, a new component is added to a schematic and needs to be included in the layout. This section describes how to forward annotate changes in a gEDA schematic to a PADS PowerPCB layout.<br/> PADS implements forward annotation through the use of an ECO (Engineering Change Order) file. The ECO file describes the differences between a current design and the desired design. PADS generates the ECO file by performing a netlist comparison between a new netlist file and the netlist contained in the current layout. </p> </div> <!-- EDIT2043 SECTION "Overview" [273-936] --> <h2 class="sectionedit2044"><a name="detailed_forward_annotation_procedure" id="detailed_forward_annotation_procedure">Detailed Forward Annotation Procedure</a></h2> <div class="level2"> <p> This procedure assumes you have a board layout open in PADS and that you have made your schematic changes in gschem. For the purposes of illustration, assume your schematic is split into two pages in the files pg1.sch and pg2.sch. </p> <ul> <li class="level1"><div class="li"> Create an updated PADS netlist by running:<br/> <strong><code>gnetlist -g pads -o mynet.asc pg1.sch pg2.sch</code></strong><br/> This will create the netlist file <strong><code>mynet.asc</code></strong>.</div> </li> <li class="level1"><div class="li"> Make a backup copy of your PADS layout in case things fail in a destructive way.</div> </li> <li class="level1"><div class="li"> From within PADS, choose the “Tools → Compare Netlist” menu item and choose the following options in the form:</div> </li> </ul> <div class="table sectionedit2045"><table class="inline"> <tr class="row0"> <td class="col0">original design to compare</td><td class="col1">use current PCB design</td> </tr> <tr class="row1"> <td class="col0">new design with changes</td><td class="col1">mynet.asc</td> </tr> <tr class="row2"> <td class="col0">√</td><td class="col1">generate differences report</td> </tr> <tr class="row3"> <td class="col0">√</td><td class="col1">generate eco file</td> </tr> <tr class="row4"> </tr> <tr class="row5"> <td class="col0" colspan="2">comparison options</td> </tr> <tr class="row6"> <td class="col0">√</td><td class="col1">compare only ECO registered parts</td> </tr> <tr class="row7"> <td class="col0" colspan="2"> </td> </tr> <tr class="row8"> <td class="col0" colspan="2">attribute comparison level</td> </tr> <tr class="row9"> <td class="col0">√</td><td class="col1">ignore all attributes</td> </tr> </table></div> <!-- EDIT2045 TABLE [1578-1852] --> <p> Click the OK button to create the ECO file. </p> <ul> <li class="level1"><div class="li"> Examine the ECO file to make sure it looks ok (the ECO file is a text file which can be viewed with any text editor).</div> </li> <li class="level1"><div class="li"> From within PADS, choose the “File → Import…” menu item. Locate and choose the ECO file created previously.</div> </li> </ul> </div> <!-- EDIT2044 SECTION "Detailed Forward Annotation Procedure" [937-2135] --> <h2 class="sectionedit2046"><a name="back_annotation_of_pads_powerpcb_layout_changes_to_geda_schematic" id="back_annotation_of_pads_powerpcb_layout_changes_to_geda_schematic">Back Annotation of PADS PowerPCB Layout Changes to gEDA Schematic</a></h2> <div class="level2"> <p> Backannotation is the process of updating schematics to reflect changes made in the layout. This process is used, for example, when the reference designators have been renumbered on the layout, when pins have been swapped (e.g., on an AND gate), or slots have been swapped (e.g., on a multi-gate package). This section describes how to backannotate changes in a PADS PowerPCB layout to a gEDA schematic. The PADS PowerPCB tool supports three types of schematic backannotation: </p> <ol> <li class="level1"><div class="li"> Reference designator changes. This is often times used at the end of a layout to give components which are geographically close a set of reference designators which are numerically close.</div> </li> <li class="level1"><div class="li"> Slot swapping. This is commonly found in digital designs where there may be multiple identical gates in a single package. For example, you may wish to swap which slot is used in a hex inverter.</div> </li> <li class="level1"><div class="li"> Pin swapping. During layout, the designer may wish to swap equivalent pins on a chip. For example, the two inputs on a NAND gate.</div> </li> </ol> <p> Currently only reference designator changes are automatically processed by the PADS to gschem backannotation tool. The slot and pin swapping changes are provided in a report which the schematic designer must use to manually correct the schematic. </p> </div> <!-- EDIT2046 SECTION "Back Annotation of PADS PowerPCB Layout Changes to gEDA Schematic" [2136-3463] --> <h3 class="sectionedit2047"><a name="detailed_backannotation_procedure" id="detailed_backannotation_procedure">Detailed Backannotation Procedure</a></h3> <div class="level3"> <p> This procedure assumes you have a board layout open in PADS. For the purposes of illustration, assume your schematic is split into two pages in the files pg1.sch and pg2.sch. </p> <ul> <li class="level1"><div class="li"> Create an up to date PADS netlist by running:<br/> <strong><code>gnetlist -g pads -o mynet.asc pg1.sch pg2.sch</code></strong><br/> This will create the netlist file <strong><code>mynet.asc</code></strong>.</div> </li> <li class="level1"><div class="li"> From within PADS, choose the “Tools → Compare Netlist” menu item and choose the following options in the form:</div> </li> </ul> <div class="table sectionedit2048"><table class="inline"> <tr class="row0"> <td class="col0">original design to compare</td><td class="col1">mynet.asc</td> </tr> <tr class="row1"> <td class="col0">new design with changes</td><td class="col1">use current PCB design</td> </tr> <tr class="row2"> <td class="col0">√</td><td class="col1">generate differences report</td> </tr> <tr class="row3"> <td class="col0">√</td><td class="col1">generate eco file</td> </tr> <tr class="row4"> <td class="col0" colspan="2"> </td> </tr> <tr class="row5"> <td class="col0" colspan="2">comparison options</td> </tr> <tr class="row6"> <td class="col0">√</td><td class="col1">compare only ECO registered parts</td> </tr> <tr class="row7"> <td class="col0" colspan="2"> </td> </tr> <tr class="row8"> <td class="col0" colspan="2">attribute comparison level</td> </tr> <tr class="row9"> <td class="col0">√</td><td class="col1">ignore all attributes</td> </tr> </table></div> <!-- EDIT2048 TABLE [3961-4236] --> <p> Click the OK button to create the ECO file. </p> <ul> <li class="level1"><div class="li"> Examine the ECO file to make sure it looks ok (the ECO file is a text file which can be viewed with any text editor).</div> </li> <li class="level1"><div class="li"> Make a backup copy of your gEDA schematic files in case things fail in a destructive way.</div> </li> <li class="level1"><div class="li"> Run:<br/> <strong><code>pads_backannotate file.eco pg1.sch pg2.sch | tee backanno.log</code></strong><br/> where <strong><code>file.eco</code></strong> is the name of the ECO file created previously and <strong><code>pg1.sch</code></strong> and <strong><code>pg2.sch</code></strong> are all of your schematic pages. This will apply the reference designator change portion of the ECO file and also generate a list of pin and slot swapping which must be performed by hand. The file <strong><code>backanno.log</code></strong> will contain a log of the session that can be refered to when performing the pin and slot swapping.</div> </li> </ul> </div> <!-- EDIT2047 SECTION "Detailed Backannotation Procedure" [3464-] --></body> </html>
distrib
>
Mageia
>
5
>
x86_64
>
media
>
core-release
>
by-pkgid
>
f2f28f61487f3042d93877451f0a311f
>
files
>
62
