Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 13911
  • 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

DefOut issue

KVBABU

 Hi all,

 

       In my design , i have many tielow & tiehigh less. Among them some them belongs to spare modules also . I had kept dont touch constraint on the tieoff cells where ever required. I dont have any issue with tie-hi cells. But, when i queried for attibute of   the nets associated with  tie-low cells , the tool is displaying the message that the respective net is a regular net. When i try to dump out def file the design, i obeserved the same net in special net section.

Why it is comming like that ? could anyone of you explain me ?

 Thgank you  in advance,

Regards,

K.VISWANADH BABU 

 

  •  Did you happen to hand-route the tielo nets with a wider width than default? That would put them in the SPECIALNETS section. Can you cut and paste the DEF section of the net?

  •  Hi kari,

    Thank you for your response.

    But, i  had routed tielow nets using only default rules in lef file. Even these nets appear both in special nets section and in normal nets section.

    Anyway iam here by pasting , its syntax from def file:

     Same net is present both in special nets and normal nets as shown below:

    Special Nets

     - IRX/IRXDIG/IRX0D/ICDR_LOG/usg_cdr/tieoff_LTIELO_23_NET
      ( IRX/IRXDIG/IRX0D/ICDR_LOG/usg_cdr/U1422 A1 )
      ( IRX/IRXDIG/IRX0D/ICDR_LOG/usg_cdr/U1422 B1 )
      ( IRX/IRXDIG/IRX0D/ICDR_LOG/usg_cdr/U1422 B2 )
      ( IRX/IRXDIG/IRX0D/ICDR_LOG/usg_cdr/U1005 CP )
      ( IRX/IRXDIG/IRX0D/ICDR_LOG/usg_cdr/U1005 D )
     ;
    Nets

     - IRX/IRXDIG/IRX0D/ICDR_LOG/usg_cdr/tieoff_LTIELO_23_NET
      ( IRX/IRXDIG/IRX0D/ICDR_LOG/usg_cdr/tieoff_LTIELO_23 ZN )
      + ROUTED M2 ( 275660 1117200 ) ( 276500 * ) VIA12_2cut_N
        NEW M3 ( 276500 1114680 ) ( * 1116920 ) VIA23_1cut
        NEW M2 ( 276500 1116920 ) ( 277060 * ) VIA12_1cut
        NEW M2 ( 276500 1116920 ) ( * 1117200 )
        NEW M3 ( 261940 1114680 ) ( * 1117200 ) VIA23_1cut
        NEW M2 ( 261940 1114680 ) ( 267820 * ) VIA12_1cut
        NEW M2 ( 267820 1114680 ) ( 276500 * ) VIA23_1cut
        NEW M2 ( 257740 1117200 ) ( 259140 * ) VIA12_1cut_V
        NEW M2 ( 259140 1117200 ) ( 261940 * )
        NEW M2 ( 275660 1117200 ) VIA12_1cut
        NEW M3 ( 261940 1114680 ) VIA23_1cut
        NEW M2 ( 257740 1117200 ) VIA12_1cut
     ;

    Regards,

    K.VISWANADH BABU 

     

  •  Something definitely looks wrong here. You have the same net name in both sections, but the connections of the net are not the same in both. Can you run Verify Connectivity on just this net to see if Encounter thinks the net is complete?

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.