Stats

  • Locked Locked
  • Replies 4
  • Subscribers 92
  • Views 13684
  • 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

Issues in shielding

PramodSabnis

 I am facing this peculiar issue while trying to do shielding on clock nets.

 The flow followed is as follows:

- Set attributes on clock nets

- Apply the attribute in clock spec file

 

I also set the following variables:

- setNanoRouteMode -routeDeferredShield true

Router carries out shielding at the end of routing. However, what I see is that this ends with a plenty of "Wire Extension" category of DRCs on ths shield nets (not the shielded ones).

Has anyone seen this behaviour? How do I fix these violations in an automated manner (there are plenty of those so, manual fix is ruled out)?

 

Best regards,

Pramod

Parents

  • Hello Bob,

    Thanks for responding.

    Well, I was using SOC8.1. Not sure which exact version it is. This is what I found from logfile:

    @(#)CDS: First Encounter v08.10-s207_1 (32bit) 03/03/2009 17:59 (Linux 2.6)
    @(#)CDS: NanoRoute v08.10-s073 NR090226-1110/USR59-UB (database version 2.30, 71.1.1) {superthreading v1.11}
    @(#)CDS: CeltIC v08.11-s187_1 (32bit) 02/26/2009 16:16:51 (Linux 2.6.9-67.0.10.ELsmp)
    @(#)CDS: CTE v08.10-s163_1 (32bit) Mar  3 2009 15:23:39 (Linux 2.6.9-67.0.10.ELsmp)
    @(#)CDS: CPE v08.11-s010
    --- Starting "First Encounter v08.10-s207_1" on Mon Oct 19 01:32:46 2009 (mem=63.4M) ---

    If you could suggest me the version to be downloaded, i could try using it.

    Meanwhile, we saw two issues in the present case;

    - The LEF was wire extension based. This should have been Via Enclosure based

    - Problem was only when the tool was jogging to MET6 to hook up shield to power i.e. VSS

    What we did was, we added complete routing blockage on MET6 and above and ran createShield. That way, the router was forced to carry out the entire shielding on MET3,4 and 5.

    This was thanks to suggestion from Cadence AE.

    However, I would like to have the above done automatically and not bother to do it in every timing iteration.

    Thanks for your inputs as well. I will try to use the version of tool you have suggested and keep this posted.

    Best regards,

    Pramod

Reply

  • Hello Bob,

    Thanks for responding.

    Well, I was using SOC8.1. Not sure which exact version it is. This is what I found from logfile:

    @(#)CDS: First Encounter v08.10-s207_1 (32bit) 03/03/2009 17:59 (Linux 2.6)
    @(#)CDS: NanoRoute v08.10-s073 NR090226-1110/USR59-UB (database version 2.30, 71.1.1) {superthreading v1.11}
    @(#)CDS: CeltIC v08.11-s187_1 (32bit) 02/26/2009 16:16:51 (Linux 2.6.9-67.0.10.ELsmp)
    @(#)CDS: CTE v08.10-s163_1 (32bit) Mar  3 2009 15:23:39 (Linux 2.6.9-67.0.10.ELsmp)
    @(#)CDS: CPE v08.11-s010
    --- Starting "First Encounter v08.10-s207_1" on Mon Oct 19 01:32:46 2009 (mem=63.4M) ---

    If you could suggest me the version to be downloaded, i could try using it.

    Meanwhile, we saw two issues in the present case;

    - The LEF was wire extension based. This should have been Via Enclosure based

    - Problem was only when the tool was jogging to MET6 to hook up shield to power i.e. VSS

    What we did was, we added complete routing blockage on MET6 and above and ran createShield. That way, the router was forced to carry out the entire shielding on MET3,4 and 5.

    This was thanks to suggestion from Cadence AE.

    However, I would like to have the above done automatically and not bother to do it in every timing iteration.

    Thanks for your inputs as well. I will try to use the version of tool you have suggested and keep this posted.

    Best regards,

    Pramod

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.