Stats

  • Locked Locked
  • Replies 5
  • Subscribers 64
  • Views 16463
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Pin labels in Virtuoso from Encounter OA

nevsan
I'm trying to get a mixed signal environment up and running. I can save the Encounter database to OA using an interoperable PDK (standard cell/routing tech lef in OA referencing base PDK). The layout looks fine in Virtuoso, but one thing that I am missing is pin labels (the kind I need for LVS). The wierd thing is that if I stream the design out from Encounter to GDSII and then stream it in, all of the pin labels are there on the proper layers. They just don't show up in the OA layout (doesn't matter whether I use saveDesign or oaOut).
  • I'm trying to get a mixed signal environment up and running. I can save the Encounter database to OA using an interoperable PDK (standard cell/routing tech lef in OA referencing base PDK). The layout looks fine in Virtuoso, but one thing that I am missing is pin labels (the kind I need for LVS). The wierd thing is that if I stream the design out from Encounter to GDSII and then stream it in, all of the pin labels are there on the proper layers. They just don't show up in the OA layout (doesn't matter whether I use saveDesign or oaOut).

  • If I understand you right you create labels in Virtuoso but they are not visible in EDI open the Design.

    On which purpose do you create the labels?

    In EDI direct after startup you could set the setOaxMode with the option -textPurpose <purpose name>

    -textPurpose purpose_name
                  Specifies  the  purpose  name that will be used when text labels
                  are written.

                  By default, any text label created in EDI System (typically  via
                  the   add_text   command) is automatically mapped to the drawing
                  purpose. Use the -textPurpose parameter to map the  text  labels
                  to a user-defined purpose.

                  Default: drawing

    Or is the issue to create Labels?

    If you login into support.cadence.com search for the solution with the ID Number: 20070208.

    Kind Regards,

    Andreas

  • Here's what I settled on for an export script that has pin labels

        setOaxMode -textPurpose label
        set labels {}
        set orientations [dict create R0 R270 R90 R0 R180 R90 R270 R180]
        foreach term [list {*}[dbGet top.terms] {*}[dbGet top.pgTerms]] {
            lappend labels [add_text -label {*}[dbGet $term.name] -height 0.5 -alignment centerLeft \
                                -pt [dbGet $term.pt] -layer [dbGet $term.layer.name] \
                                -orient [dict get $orientations [dbGet $term.orient]]]
        }

        # Stream into OA

        oaOut lib cell view -autoRemaster 

        # Remove labels

        foreach label $labels {dbDeleteObj $label} 

  • If you see an issue please file a Service case at support.cadence.com.

     

    Kind Regards,

    Andreas

  • Thanks. Given what I've read, it seems to be more of a missing feature than a bug. I'm really quite surprised that this little piece of the Mixed Signal interoperability puzzle isn't naturally part the EDI => Virtuoso workflow. We can't LVS the block by itself without pin labels and I can't get my layouters using Layout-L to connect to it correctly without pin labels. Hopefully my script will help out others that want a more complete export out of EDI and into OA.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.