( ESNUG 387 Item 2 ) --------------------------------------------- [01/23/02]

Subject: ( ESNUG 386 #3 ) Simplex, Star-RC, HSIM, Calibre, Spectre, & SPICE

> There is no known Calibre/Star-RC flow.  Avanti and Mentor have been
> discussing the possibility of this flow.  I'm curious if other readers
> would be interested in it; we are very willing to do this if customers
> request it.  Star-RC (and Star-RCXT) right now only reads LVS data
> from Hercules.
>
>     - John Lee
>       Avanti                                     Fremont, CA


From: "Joel Jensen" <JensenJ@sharpsec.com>

I use Calibre for LVS and Star-RC (not XT) for extraction and would like to
use the two together for custom designs.

Count my vote.

    - Joel Jensen
      Sharp Microelectronics                     Camas, WA

         ----    ----    ----    ----    ----    ----   ----

From: "Grego Sanguinetti" <grego@accelerant.net>

Hi, John,

Please count us in as an interested customer.

We will soon be attempting to do an evaluation of LPE tools.  The two tools
at the top of the stack are Simplex and Avanti.  We currently own Calibre LVS
but not Hercules.  It's going to be difficult to do an eval of Star-RCXT
without getting netname correspondance information out of an LVS run.

Simplex claims to be able to do this.

Ultimately we would like to get a backannotated netlist so that we can feed
it into either Spectre or Hsim, which is what we currently do with Xcalibre.

Our semicustom flow will be easier to deal with because it will be able to
use *SPF type output.

But we are a mixed signal house.  At one point or another we have to get
down to a transistor level and get as accurate as possible.

We are currently taking the SPICE netlist output from Xcalibre LPE/LVS runs
and doing our own netlist reduction and inductor extraction.  We then
rebuild the SPICE netlist (to include whichever LPE subcircuit the user
wants) and feed it the recombined netlist to HSIM.  If the user wants to
use Spectre or SpectreRF, then we use a tool built around Gemini to map
naming so that they can do hierarchical probing.  That way we can probe
internal nodes without having to know which nodes are of interest prior
to the LPE run.

It is always tough evaluating LPE tools at the transistor level, but having
a correspondence file to start with gives you a head start.  Otherwise
it is a daunting task to figure out what you are looking at.

    - Grego Sanguinetti
      Accelerant Networks, Inc.


 Sign up for the DeepChip newsletter.
Email
 Read what EDA tool users really think.


Feedback About Wiretaps ESNUGs SIGN UP! Downloads Trip Reports Advertise

"Relax. This is a discussion. Anything said here is just one engineer's opinion. Email in your dissenting letter and it'll be published, too."
This Web Site Is Modified Every 2-3 Days
Copyright 1991-2024 John Cooley.  All Rights Reserved.
| Contact John Cooley | Webmaster | Legal | Feedback Form |

   !!!     "It's not a BUG,
  /o o\  /  it's a FEATURE!"
 (  >  )
  \ - / 
  _] [_     (jcooley 1991)