Stats

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

HELP for WARN: (SOCDB-2078)

JZ Huo
 

      In the cusomter design,  some output port/pin are assigned to 1`b0 or  1`b1 .  So Encounter use tieLo/tieHi cell for them.   However,  Encounter gives the WARN: SOCDB-2078.

 

**WARN: (SOCDB-2078):   Output pin ZN of instance cortexr4_innowrapper_TIEHILO_LTIELO_15 is connected

to ground net ARPROTM[1].  This can create a short circuit if the output is 1.  Check the connectivity

 in the netlist.

**WARN: (SOCDB-2078):   Output pin Z of instance cortexr4_innowrapper_TIEHILO_LTIEHI_2 is connected to

 power net RREADYM.  This can create a short circuit if the output is 0.  Check the connectivity in th

e netlist.

**WARN: (SOCDB-2078):   Output pin ZN of instance cortexr4_innowrapper_TIEHILO_LTIELO_16 is connected

to ground net BRESPS[0].  This can create a short circuit if the output is 1.  Check the connectivity

in the netlist.

 

The ARPROTM[1] RREADYM BRESPS [0] are the output pins which are assigned to 1`b0 or 1`b1 in Netlist  .

 

The question is it seems  Encounter does NOT route these nets, so we get LVS fail in PVS.

 

===================================================================================================

=================================

 

Labeled Schematic Pin     | Matched Layout Pin     | Matched Layout Net   

--------------------------+------------------------+-----------------------

AWIDM[3]                  | <Missing>              | X31/5782             

AWIDM[2]                  | <Missing>              | X31/5783             

AWIDM[1]                  | <Missing>              | X31/5784             

AWLENM[3] .  .  .  .  .  .| <Missing> .  .  .  .  .| X31/5785             

AWSIZEM[2]                | <Missing>              | X31/5787             

AWBURSTM[1]  .  .  .  .  .| <Missing> .  .  .  .  .| X31/5788             

AWBURSTM[0]               | <Missing>              | X31/6044             

AWLOCKM[1]   .  .  .  .  .| <Missing> .  .  .  .  .| X31/5789             

AWPROTM[2]                | <Missing>              | X31/5790             

AWPROTM[1]   .  .  .  .  .| <Missing> .  .  .  .  .| X31/5791             

WIDM[3]                   | <Missing>              | X31/5792             

WIDM[2]   .  .  .  .  .  .| <Missing> .  .  .  .  .| X31/5793             

WIDM[1]                   | <Missing>              | X31/5794             

BREADYM   .  .  .  .  .  .| <Missing> .  .  .  .  .| X31/6045             

ARIDM[3]                  | <Missing>              | X31/5795             

ARLENM[3] .  .  .  .  .  .| <Missing> .  .  .  .  .| X31/5798             

ARSIZEM[2]                | <Missing>              | X31/5799             

ARPROTM[1]   .  .  .  .  .| <Missing> .  .  .  .  .| X31/5800             

RREADYM                   | <Missing>              | X31/6046             

BRESPS[0] .  .  .  .  .  .| <Missing> .  .  .  .  .| X31/5808             

RRESPS[0]                 | <Missing>              | X31/5813             

PSLVERRDBG                | <Missing>              | X31/5847             

 
===================================================================================================

===========[cortexr4_innowrapper]

====== Summary of Errors

===================================================================================================

=================================

 

Schematic     | Layout     | Error Type             

--------------+------------+-------------------------

           22 |          - | Unmatched Pin Labels

 

Do I need use globalNetConnect  for these nets ?   or any better solution ?

 
Thanks

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.