Article View: comp.lang.vhdl
Article #439VERILOG_PROBLEM
From: eorourke
Date: Tue, 23 Jun 1992 17:28
Date: Tue, 23 Jun 1992 17:28
43 lines
2769 bytes
2769 bytes
Hello, I am doing a chip-design at Trinity College Dublin. The machine I work on is a DEC 5000/200 workstation, the system is the cadence system EDGE with a MIETEC_2.4 um cell-library released by EUROCHIP. I, or I should better say we, have got a problem with hierarchical designs when simulating them with VERILOG. There are almost everytime some unexpected compilation errors: component name (<name>) not declared For an example the message is : component name (I2a) is not declared. In the netlist there is no "I2a" but there are Instances like "AND2 I2(hnl_100, hnl_143);" The error-message is described on page 20-13 in the Verilog-Manual. This error only occurs when trying to simulate a hierarchical design. Sometimes we can remove these compilation errors if we just copy a schematic and extract it once more without any changes in the connectivity itself. But mostly, we get compilation errors with other undeclared nodes. Sometimes it really seems to be random which nodes are not declared. Having "caught" the temporary files verisave.cmdfile and verifoo.batch, we found that what was happening was that in certain random cases, the period denoting the hierarchical position was omitted by either the Cadence Schematic capture or verilog. However, the netlist generated by Cadence seems to be okay. Running the Verilog outside Cadence seems to work also. We suspect that the problem may be in the "runsim" section of the Simulation Interface. This "evidence" was found in verisave.cmdfile! In the example above, for instance, I2a should have been I2.a but the period got lost! We caught the verisave.cmdfile by using the stepwise running of SI in interactive mode during the runsim command. Is there a patch for this "bug"? Is this reported elsewhere or by other users of Eurochip Releases? Any relevant information would be appreciated! Thanks in advance... Rainer Hoehler Eugene O' Rourke orourke@mee.tcd.ie rhoehler@mee.tcd.ie
Technical Details
Message-ID:
<1992Jun23.172809.1@vax1.tcd.ie>Path:
arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!hri.com!snorkelwacker.mit.edu!bloom-beacon!eru.mt.luth.se!lunic!sunic2!mcsun!ieunet!tcdcs!vax1.tcd.ie!eorourkeShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 116545,b3c41b4b209d1de,start X-Google-Attributes: gid116545,public X-Google-Thread: 1089ad,b3c41b4b209d1de,start X-Google-Attributes: gid1089ad,public X-Google-ArrivalTime: 1992-06-22 21:46:14 PST Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!hri.com!snorkelwacker.mit.edu!bloom-beacon!eru.mt.luth.se!lunic!sunic2!mcsun!ieunet!tcdcs!vax1.tcd.ie!eorourke From: eorourke@vax1.tcd.ie Newsgroups: comp.lang.vhdl,eunet.esprit.eurochip Subject: VERILOG_PROBLEM Message-ID: <1992Jun23.172809.1@vax1.tcd.ie> Date: 23 Jun 92 17:28:09 GMT Article-I.D.: vax1.1992Jun23.172809.1 Sender: usenet@cs.tcd.ie (NN required at ashe.cs.tcd.ie) Organization: Trinity College Dublin Lines: 43 Nntp-Posting-Host: vax1.tcd.ie