• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Problems Importing OA Design from Virtuoso into Encount...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 91
  • Views 13151
  • 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

Problems Importing OA Design from Virtuoso into Encounter

TruLogic
TruLogic over 14 years ago

Hello, 

While trying to perform place and route using Encounter I'm "encountering" errors importing my design from Virtuoso. When I try to import the design, I get the following:

Reading tech data from OA Library 'NCL' ...
FE units: 0.001 microns/dbu, OA units: 0.001 microns/dbu, Conversion factor: 1
**WARN: (ENCOAX-775):   Layer 'OVERLAP' has already been defined in Encounter database, the contents will be skipped.
**WARN: (ENCOAX-713):   Unsupported Layer direction for layer 'RX'. Check the layer information in OA technology database.
**ERROR: (ENCOAX-719):  Pitch of layer 'RX' is 0. Check the layer information in OA technology database.
**ERROR: **ERROR: (ENCSYT-16006):       Error in reading LEF information from OA reference libraries. Check the OA database provided.

RX is the active layer and should not be routable, however, Encounter is looking for pitch information. This layer should not be used in place and route at all. The only reason I can think of that Encounter might need it would be in RX_M1 vias. How do I tell Ecnounter to ignore this layer? Could I change the prRules section of my technology file? Here is that section of my tech file:

prRules(

 prRoutingLayers(
 ;( layer                       preferredDirection  )
 ;( -----                       ------------------  )
  ( PC                           "halfRoute" )
  ( RX                           "halfRoute" )
  ( M1                           "horizontal" )
  ( M2                           "vertical" )
  ( M3                           "horizontal" )
  ( M4                           "vertical" )
  ( M5                           "horizontal" )
  ( M6                           "vertical" )
  ( M1_2B                        "horizontal" )
  ( M2_2B                        "vertical" )
 ) ;prRoutingLayers

 prViaTypes(
 ;( device viewName             viaType    )
 ;( ---------------             -------    )
  ( ("PC_M1" "symbolic")    "default"  )
  ( ("RX_M1" "symbolic")    "default"  )
  ( ("M1_M2" "symbolic")    "default"  )
  ( ("M2_M3" "symbolic")    "default"  )
  ( ("M3_M4" "symbolic")    "default"  )
  ( ("M4_M5" "symbolic")    "default"  )
  ( ("M5_M6" "symbolic")    "default"  )
  ( ("M6_M1_2B" "symbolic")    "default"  )
  ( ("M1_2B_M2_2B" "symbolic")    "default"  )
 ) ;prViaTypes

 prRoutingPitch(
 ;( layer                pitch )
 ;( -----                ----- )
  ( "M1"         (plus (techParam "grM1Width") (techParam "grM1Space")) )
  ( "M2"         (plus (techParam "grM2Width") (techParam "grM2Space")) )
  ( "M3"         (plus (techParam "grM3Width") (techParam "grM3Space")) )
  ( "M4"         (plus (techParam "grM4Width") (techParam "grM4Space")) )
  ( "M5"         (plus (techParam "grM5Width") (techParam "grM5Space")) )
  ( "M6"         (plus (techParam "grM6Width") (techParam "grM6Space")) )
  ( "M1_2B"         (plus (techParam "grM1_2BWidth") (techParam "grM1_2BSpace")) )
  ( "M2_2B"         (plus (techParam "grM2_2BWidth") (techParam "grM2_2BSpace")) )
 ) ;prRoutingPitch

) ;prRules

 

 

Thank you for your help.

  • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information