Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13314
  • 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

*ERROR: (ENCOAX-41): Cannot create an instance in a hierarchy where the occurrences are not unique

konx

 Hello,

 I have a P&R-ed design (let's call it MultiA) in Encounter with no violations. I'm trying to export it in Virtuoso using OA database. While doing this, I receive the following errors:

**ERROR: (ENCOAX-41):   Cannot create an instance in a hierarchy where the occurrences are not unique
**ERROR: (ENCOAX-347):  Could not create instance 'pixel_7/FILLER_impl0_19' in OA. Refer to any earlier messages.

 The final result is then a design _without_ fillers. The other cells are anyway present.

You should notice that:

- I can successfully export another design (in the same OA library). Let's say this is called SingleA.

- The wrong design(MultiA) contains many instances of design SingleA. I'm reading in the netlist of design SingleA and then I'm placing many copies of this design.

 

Could you please point to what might be the error source?

 

Thanks in advance for the help,

 

Francesco

 

  • Hi Francesco,

    How are the technology and libraries being read in? Are they defined with LEF or OA? If they are defined with LEF then that is likely the problem. You can't save a design to OA when the libs are defined with LEF. Use lefin to translate them to OA then reference them when reading the design into EDI System.

    For example, to convert the LEF files to OA:

    lefin -lef tech.lef -lib oaLib
    lefin -lef stdcells.lef -lib oaLib
    ...


    Then during design import comment out the variable pointing to the LEF file and replace it with:

    set init_oa_ref_lib {oaLib}
    set init_abstract_view {abstract}


    If you're using EDI 10.1 or earlier the config file vars are:

    set rda_Input(ui_oa_reflib) {oaLib}
    set rda_Input(ui_oa_abstractname) {abstract}

    Regards,

    Brian

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.