Usage model¶

State dependent power analysis mode¶

MCMM power analysis usage model¶

Please check regression case "qa_report_power_analysis_mcmm1"

Method 1:

current—mcmm {func—ss—rcmax scan—ff—rcmin} 
compute—timing
report—power—analysis -working—scenario func—ss—rcmax 
report—power—analysis -working—scenario scan—ff—rcmin

Method 2:

current—mcmm {func—ss—rcmax scan—ff—rcmin} 
compute—timing
set—working—scenario func—ss—rcmax 
report—power—analysis      
set—working—scenario sccan—ff—rcmin 
report—power—analysis

Vector based power analysis:¶

Below will align with reference behavior:

髻 align all the vcd time to 江ero set—app—var pow vcd—align true
髻 other option:
align—vcd test.vcd -start—time 123
髻 select power window
report—window—power -window—si江e xxx -step—si江e xxx -module—map—file xxx 
report—window—power -window—si江e xxx -step—si江e xxx -single—vcd—file xxx

Power annotation flow: (Under development) ref ticket #7955¶

髻 convert ref power file to VP readable command 
convert—emir—power xxx xxx.tcl
髻 in the xxx.tcl we have a set of command which has:
set—emir—power cellName -frequency freq -toggle—rate tr -leakage—power lp -switching—power sp -int ernal—power ip
髻 later we will use the command to derive IR ...

To change cap mode mode:¶

髻 default is cap range, which is to correlate PXXX 
set—app—var cap—usage rangelrise—fallldefault

Power param¶

1. effsw_use_initial default: false
   false: use condition number calc effse
true: use initial way calc effsw

2. power_mode default: 0
   0: sdp mode
1: avg_fast mode

3. trans_use_max default: false
   false:rise and fall internalpower use themself max trans to lookup
true: rise and fall internalpower use max trans to lookup

4. result_calc_way default: 0
   0: worst val * arcNum
1: worst(relatedPinA)*arcNum(relatedPinA) + worst(relatedPinB)*arcNum(relatedPinB) ... worst(relatedPinN)*arcNum(relatedPinN)

About glitch ans switching activity propagation