Home > Community > Forums > Digital Implementation > CelticSignalStorm vs. AAE, holdviolations

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: *

 CelticSignalStorm vs. AAE, holdviolations 

Last post Wed, May 7 2014 2:53 AM by marten. 0 replies.
Started by marten 07 May 2014 02:53 AM. Topic has 0 replies and 1528 views
Page 1 of 1 (1 items)
Sort Posts:
  • Wed, May 7 2014 2:53 AM

    • marten
    • Top 500 Contributor
    • Joined on Thu, Aug 8 2013
    • Bielefeld, Nrth Rhine Westfalia
    • Posts 23
    • Points 370
    CelticSignalStorm vs. AAE, holdviolations Reply
    Hi there,

    we are using Encounter 13.1 and changed the from SignalStorm flow to AAE flow.
    While porting our scripts we found out, that even if AAE optimizes the design and fixes all hold violations,
    SignalStorm still finds hold violations. So is SignalStorm more pessimistic?
    We now use the following script for postRoute optimization:

    ...
    setAnalysisMode -analysisType onChipVariation -cppr both
    setDelayCalMode -SIAware true -engine default

    # In-Place-Optimization
    setOptMode -usefulSkew true

    #step -> optimizatzion effort

    for {set step 0} {$step <= $Effort} {incr step} { 
        if {$step==0} {
            optDesign -postRoute
           if { $::SOC_FIX_HOLD == 1 } {
               optDesign -postRoute -hold
               }
           } else {
               optDesign -postRoute -incr
               if { $::SOC_FIX_HOLD == 1 } {
                   optDesign -postRoute -hold -incr
                   }
           }
    }

    #switch engine to use slow but more accurate Signal Storm optimization
    #for setup and hold optimization with signal integrity optimization enabled

    setDelayCalMode -engine signalStorm -SIAware false
    optDesign -postRoute
    if { $::SOC_FIX_HOLD == 1 } {
        optDesign -postRoute -hold
        }
    if { $::SOC_FIX_HOLD == 1 } {
        optDesign -postRoute -hold -si
       }
    optDesign -postRoute -si
    }

    So our question is, why are there still hold violations using AAE for optimization and SGS for timing analysis?
    Is our flow the right way or do you have any suggestions for handling this issue ?

    Kind regards,
    Marten
    • Post Points: 5
Page 1 of 1 (1 items)
Sort Posts:
Started by marten at 07 May 2014 02:53 AM. Topic has 0 replies.