• 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. Custom IC Design
  3. Diva extraction error with Digital BlackBox cells ?

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 13483
  • 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

Diva extraction error with Digital BlackBox cells ?

isazulkc
isazulkc over 13 years ago
Hi,
I have a very strange problem when extracting my design with diva. I'm working on a Mixed-Signal ASIC using some Artisan IP cells as BlackBox.
Diva Extraction sometimes fails, sometimes pass on the same top layout view. Here is an example of the display error in the CIW:
""..............
 \o executing: nwelldiode = geomAnd(nwelldiode1 nwell)
\o executing: metal5I = geomAndNot(metal5I inductor)
\o executing: metal6I = geomAndNot(metal6I inductor)
\o executing: act = geomOr(ohmic diff)
\o executing: geomConnect((via contact poly1I metal1I ndiff pdiff diff nohmic pohmic nohmicPnpBase...
\w *WARNING* In model artisan_sc_30/OAI221X1/abstract, terminal "A0" is missing. Found at (3368.89,2864.02).
\o 5654 macro cells were extracted in this cell.
\w *WARNING* An error has occurred during processing. ""
 However, I can see the A0 in this abstract view.  This happens randomly for different Digital BlackBox cell (DFF, NAND, ...)
 The error occurs always in the connectivity execution  geomConnect. In the divaEXT.rul file, the full command for connectivity is:
geomConnect(
       via(contact poly1I metal1I ndiff  pdiff diff nohmic pohmic nohmicPnpBase pnpEmitter ohmic act)
       via(rfndiffCon ndiff drainndiff)   
       via(rfndiffCon ndiff sourcendiff)  
       via(rfndiffCon ndiff rfndiff)
       via(rfpdiffCon pdiff sourcepdiff) 
       via(rfpdiffCon pdiff drainpdiff) 
       via(rfpdiffCon pdiff rfpdiff)    
       via(rfpoly1ICon poly1I rfpoly1I) 
     via(sub2bkgnd sub bkgnd)  
     via(contnohmicnwell nohmic nwell) 
     via(contpnpBase nohmicPnpBase pnpBase)
     via(contpohmicsub pohmic sub)  
     via(contpohmicsub pohmic rw) 
     via(obutcont butcontact ohmic)    
     via(dbutcont butcontact diff)     
      via(via12 metal1I metal2I)        
      via(via23 metal2I metal3I)     
      via(via34 metal3I metal4I)
      via(via45 metal4I metal5I)
      via(via56 metal5I metal6I)
      via(via56ctm ctm metal6I)
      label("poly1" poly1I)
      label("metal1" metal1I)
      label("metal2" metal2I)
      label("metal3" metal3I)
      label("metal4" metal4I)
      label("metal5" metal5I)
      label("metal6" metal6I)
   ) ;end geomConnect()
  Any idea to solve this problem ?
 Best Regards !
 KC
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    KC,

    I've only seen reports of this in very old versions, and in fact one of the most recent matches I found was something fixed in IC5033. That was to do with hierarchical properties on the macro instance in the layout.

    Most likely you'll need to report this to Customer Support so that an AE can take a look at the data.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    KC,

    I've only seen reports of this in very old versions, and in fact one of the most recent matches I found was something fixed in IC5033. That was to do with hierarchical properties on the macro instance in the layout.

    Most likely you'll need to report this to Customer Support so that an AE can take a look at the data.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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