• 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. Logic Design
  3. lec nonequivalent on bi-di IO Pad

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 62
  • Views 13106
  • 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

lec nonequivalent on bi-di IO Pad

Arcade9999
Arcade9999 over 15 years ago

Dear all,

Currently I'm doing the whole chip rtl to netlist LEC.
There are some noneqivalent points happen on bi-directional IO Pad.

The following is the noneq report message:

Compared points are: Non-equivalent
  (G) + 586   PO   /SDATA_0
  (R) + 586   PO   /SDATA_0

Compared points are: Non-equivalent
  (G) + 1198  BBOX /PAD_SDATA_0
  (R) + 1196  BBOX /PAD_SDATA_0
Due to these Non-equivalent points:
[INPUT]
  (G) + 11256 BUF  /PAD_SDATA_0/IO
  (R) + 8037  BUF  /PAD_SDATA_0/IO
 

 And the following is the diagnosis message:

1. Diagnosis for Non-equivalent key points:
  (G) + 575   PO   /SDATA_0
  (R) + 575   PO   /SDATA_0
There are extra unmapped key points in this logic cone
================================================================================
          ID     Type                Name
--------------------------------------------------------------------------------
   (G)   49     'PI(Z)'             /SDATA_0_z
   (R)   49     'PI(Z)'             /SDATA_0_z
================================================================================


The diagnosis point can be corrected by changing the following gates:
================================================================================
Correction             ID (R)     Type          Name
--------------------------------------------------------------------------------
DEL_INVERTER    8229      INV            /SDATA_0
FANIN_CHANGE   8230      MUX          /SDATA_0
change                 49          PI              /SDATA_0_z
to                         11406     INV           /SDATA_0  (G)
================================================================================

 

How to solve this kind of bi-di IO nonequivalent problem?

Another question is that I don't know why not all of the bi-di IO are reported nonequivalent.
Only several bi-di IO are reported.
If the bi-di IO noneq is a general problem, then all of the bi-di IO should be reported noneq.

Thank you!!

  • 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