Home > Community > Forums > Digital Implementation > reportFanoutviolations -noGlobalnet reports the fanout violations in clock gate cells and PLL outputs

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 reportFanoutviolations -noGlobalnet reports the fanout violations in clock gate cells and PLL outputs 

Last post Wed, Feb 27 2013 8:00 AM by Kari. 1 replies.
Started by gops 30 Jan 2013 08:54 AM. Topic has 1 replies and 874 views
Page 1 of 1 (2 items)
Sort Posts:
  • Wed, Jan 30 2013 8:54 AM

    • gops
    • Top 75 Contributor
    • Joined on Wed, Sep 24 2008
    • Trivandrum, Kerala
    • Posts 118
    • Points 2,505
    reportFanoutviolations -noGlobalnet reports the fanout violations in clock gate cells and PLL outputs Reply

    I tried with the option reportFanoutviolation -noglobanet. I expect all the clock nets and clock gating nets to be avoided fromt he violation report. But I found all these paths in violation report. 

     

    When I used report_clock, its reporting all the PLL outputs as clocks. Please tell me why it is thn reported in fanout violaton report when i give -noglobalnet option 

    • Post Points: 20
  • Wed, Feb 27 2013 8:00 AM

    • Kari
    • Top 10 Contributor
    • Joined on Tue, Jul 15 2008
    • Cary, NC
    • Posts 693
    • Points 14,155
    Re: reportFanoutviolations -noGlobalnet reports the fanout violations in clock gate cells and PLL outputs Reply
    Your understanding of the command is correct - please file a service request so we can see why this isn't working as expected.
    • Post Points: 5
Page 1 of 1 (2 items)
Sort Posts:
Started by gops at 30 Jan 2013 08:54 AM. Topic has 1 replies.