• 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. cdb2oa (PcellEvalFail)

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 13957
  • 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

cdb2oa (PcellEvalFail)

Peter123
Peter123 over 13 years ago

Hi Masters,

I'm facing issue when dealing with cdb2oa.

I can't retain my cdf callback after converting my layout from cdb to oa database;resulted PcellEvailFail message show up...

Below is one of the ERROR message.

ERROR   (CDBOA-603): Cellview <path>/<name> contains <object type>, <object id>.
                     This object type is not supported by OpenAccess and will
                     not be translated.

                      Generated 3 times. The CDBA database supports many objects
                     and constructs that have no OpenAccess equivalent. These
                     objects and constructs are not translated. ?? newline
                      Examples:
                      ERROR (CDBOA-603) : Cellview AN2/layout.cdb contains a
                     complex mosaic instance, IN3_1. This object type is not
                     supported by OpenAccess and will not be translated.
                      Here:
                      object_type = a complex mosaic instance object_id = IN3_1

                      ERROR (CDBOA-603): Cellview AN2/layout.cdb contains an
                     instance on a net, IN23 on Net32. This object type is not
                     supported by OpenAccess and will not be translated.
                      Here:
                      object_type = an instance on a net object_id = IN23 on
                     Net32

 

I'm currently using IC 6.15.

What can i do to retain the cdf callback?

Thanks,

Peter

 

 

  • Cancel
  • Peter123
    Peter123 over 13 years ago

    Hi Masters,

    I'm facing issue when dealing with cdb2oa.

    I can't retain my cdf callback after converting my layout from cdb to oa database;resulted PcellEvailFail message show up...

    Below is one of the ERROR message.

    ERROR   (CDBOA-603): Cellview <path>/<name> contains <object type>, <object id>.
                         This object type is not supported by OpenAccess and will
                         not be translated.

                          Generated 3 times. The CDBA database supports many objects
                         and constructs that have no OpenAccess equivalent. These
                         objects and constructs are not translated. ?? newline
                          Examples:
                          ERROR (CDBOA-603) : Cellview AN2/layout.cdb contains a
                         complex mosaic instance, IN3_1. This object type is not
                         supported by OpenAccess and will not be translated.
                          Here:
                          object_type = a complex mosaic instance object_id = IN3_1

                          ERROR (CDBOA-603): Cellview AN2/layout.cdb contains an
                         instance on a net, IN23 on Net32. This object type is not
                         supported by OpenAccess and will not be translated.
                          Here:
                          object_type = an instance on a net object_id = IN23 on
                         Net32

     

    I'm currently using IC 6.15.

    What can i do to retain the cdf callback?

    Thanks,

    Peter

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

    Peter,

    Those messages don't appear to be anything to do with CDF Callbacks, and lack of CDF Callbacks should not cause pcellEvalFail messages.

    It's saying you have complex mosaics (presumably created using the structure compiler, which was end-of-lifed some time ago).

    Anyway, best thing is to log a service request with customer support.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Prasanna7
    Prasanna7 over 11 years ago

    Hi Andrew,

    While converting main tech lib(cdb format) to oa format using command, I am getting the following errors and warnings for almost all the pcells. The error is as follows:

     ERROR   (CDBOA-612): Cell                                                        
                         ../../../../../../bicmos5hpe/V2.1.0.5/bicmos5h
                         has an illegal CDBA name. Its contents will be copied to  
                         the OpenAccess version of the library but will not be      
                         translated.

    WARNING (CDBOA-406): Directory                                                 
                         ../../../../../../bicmos5hpe/V2.1.0.5/bicmos5h
                         is in a cellview. The directory and its contents will be  
                         copied to the destination database but will not be         
                         translated.

     

    So in any layout, which contains pcells from techlib, "pcellEvailFailed" message is coming. Please help me how to overcome this error. 

     

    Thanks in Advance

    Lakshmi Prasanna

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • theopaone
    theopaone over 11 years ago

     Instead of tagging on to this very old topic, please start a new topic.

    What is the name of the llibrary you are converting? It looks like there is additional directories in the structure which would cause it to ignore the contents.

    cdb2oa expects: libDirectory/cellDirectory/viewDirectory/dataFile

     Ted

    • Cancel
    • Vote Up 0 Vote Down
    • 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