• 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. EDI -> Empty Modules

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 92
  • Views 4947
  • 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

EDI -> Empty Modules

Terry2000
Terry2000 over 12 years ago

Hello, 

First run through EDI 12.00 and I'm having a few teething problems.

Successfully synthesised the RTL to verilog netlist but when I import the design I'm getting the following warnings (all standard cells are in the verilog netlist are listed, I've trucated the listing for the post).

I've checked the LEF and the cells are included.

 Any ideas what I'm doing wrong?

**WARN: (ENCDB-2504):    Cell OR6M2XM is instantiated in the Verilog netlist, but is not defined.
**WARN: (ENCDB-2504):   Cell OR4M1XM is instantiated in the Verilog netlist, but is not defined.
**WARN: (ENCDB-2504):   Cell NR3M1XM is instantiated in the Verilog netlist, but is not defined.
**WARN: (ENCDB-2504):   Cell AO31M2XM is instantiated in the Verilog netlist, but is not defined.
**WARN: (ENCDB-2504):   Cell DFQRM1XM is instantiated in the Verilog netlist, but is not defined.
WARN: (EMS-63):       Message <ENCDB-2504> has exceeded the default message display limit of 20.

Found empty module (OR6M2XM).
Found empty module (OR4M1XM).
Found empty module (NR3M1XM).
Found empty module (AO31M2XM).
Found empty module (DFQRM1XM).
Starting recursive module instantiation check.
No recursion found.
Term dir updated for 0 vinsts of 85 cells.
Building hierarchical netlist for Cell hlt5000_toplevel ...
*** Netlist is unique.
** info: there are 91 modules.
** info: there are 0 stdCell insts.
 

  • Cancel
Parents
  • Terry2000
    Terry2000 over 12 years ago

    Hello,

    I've had a look at the cmd file generated using the file->import design. If I've understood correctly for some reason the init_lef_file variable is being set correctly then cleared.

    *** Memory pool thread-safe mode activated.
    <CMD> set conf_ioOri R0
    <CMD> set defHierChar /
    <CMD> set delaycal_input_transition_delay 0.1ps
    Set Input Pin Transition Delay as 0.1 ps.
    <CMD> set init_assign_buffer 1
    <CMD> set init_import_mode { -keepEmptyModule 1 -timerMode 1 -treatUndefinedCellAsBbox 0}
    <CMD> set init_lef_file /libs/UMC/UMxxxLSCSPMVBDS_A01/lef/uxxxlscspmvbds.lef
    <CMD> set init_oa_search_lib {}
    <CMD> set init_top_cell toplevel
    <CMD> set init_verilog r2g_output/r2g.v
    <CMD> set lsgOCPGainMult 1.000000
    <CMD> set rtl_vhdl_list {{WORK {WORK ../RTL/adc_interface.vhd ../RTL/fuse_control.vhd ../RTL/fuse_interface.vhd ../RTL/i2c_interface.vhd ../RTL/package.vhd}} {TEMP {}}}
    <CMD> set init_lef_file {}
    <CMD> init_design
    Reading netlist ...

     I entered the commands on the command line without the set init_lef_file {} and it's now trying to load the lef, it's moaning about it but at least  it's attempting to load. Thanks again for your help. 

    Loading LEF file /libs/UMC/UMxxxLSCSPMVBDS_A01/lef/uxxxlscspmvbds.lef...
    **ERROR: (ENCLF-328):   The layer 'ME1' specified in macro pin 'XOR4M8XM.A' does                                                                                    not exist
    **ERROR: (ENCLF-53):    The layer 'ME1' referenced in pin 'A' in macro 'XOR4M8XM                                                                                   ' is not found in the database. A layer must be defined in the LEF technology LA                                                                                   YER section before it can be referenced.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Terry2000
    Terry2000 over 12 years ago

    Hello,

    I've had a look at the cmd file generated using the file->import design. If I've understood correctly for some reason the init_lef_file variable is being set correctly then cleared.

    *** Memory pool thread-safe mode activated.
    <CMD> set conf_ioOri R0
    <CMD> set defHierChar /
    <CMD> set delaycal_input_transition_delay 0.1ps
    Set Input Pin Transition Delay as 0.1 ps.
    <CMD> set init_assign_buffer 1
    <CMD> set init_import_mode { -keepEmptyModule 1 -timerMode 1 -treatUndefinedCellAsBbox 0}
    <CMD> set init_lef_file /libs/UMC/UMxxxLSCSPMVBDS_A01/lef/uxxxlscspmvbds.lef
    <CMD> set init_oa_search_lib {}
    <CMD> set init_top_cell toplevel
    <CMD> set init_verilog r2g_output/r2g.v
    <CMD> set lsgOCPGainMult 1.000000
    <CMD> set rtl_vhdl_list {{WORK {WORK ../RTL/adc_interface.vhd ../RTL/fuse_control.vhd ../RTL/fuse_interface.vhd ../RTL/i2c_interface.vhd ../RTL/package.vhd}} {TEMP {}}}
    <CMD> set init_lef_file {}
    <CMD> init_design
    Reading netlist ...

     I entered the commands on the command line without the set init_lef_file {} and it's now trying to load the lef, it's moaning about it but at least  it's attempting to load. Thanks again for your help. 

    Loading LEF file /libs/UMC/UMxxxLSCSPMVBDS_A01/lef/uxxxlscspmvbds.lef...
    **ERROR: (ENCLF-328):   The layer 'ME1' specified in macro pin 'XOR4M8XM.A' does                                                                                    not exist
    **ERROR: (ENCLF-53):    The layer 'ME1' referenced in pin 'A' in macro 'XOR4M8XM                                                                                   ' is not found in the database. A layer must be defined in the LEF technology LA                                                                                   YER section before it can be referenced.

    • 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