deepika_11
Newbie level 3
- Joined
- Aug 21, 2009
- Messages
- 3
- Helped
- 0
- Reputation
- 0
- Reaction score
- 0
- Trophy points
- 1,281
- Location
- India
- Activity points
- 1,317
Hi All,
I need to build handoff checks for Implementation - So I need check for Libraries, netlist, SDC, UPF and DEF.
Checks should be the ones which impact Implementation and are not covered by people who are providing inputs -
i.e. - GCA and 0RC timing - for costraint checking will be executed by person handing over SDC
As an implmentation person, I need to write screener for PnR, capturing/covering anything/everything which will impact my QoR - at the same time making sure I am not repating checks being done by the experts (input providers)
Checks I have thought of are -
-> DEF and netlist consistency (because two different people are providng inputs, which might be clean but may not work togther)
-> Utilization report
-> congestion Map for better predictability - makes more sense if DCT is used for SYnthesis
-> check if all implementation corners are available in libraries
-> Data linking (DEF + netlist + UPF +SDC)
-> Leakage report of netlist - with summary of cells/ICGs/Vt types
-> Summary of clocks -> to check if clocks has required frequency
-> Clock domain crossing report -> to see if case analysis is ok
-> report_qor
Please suggest more checks, quick response is really appreciated. I want checks to be precise with their intent clear. Any checks worth capturing before PnR to ensure quality and completeness of input data is good.
I need to build handoff checks for Implementation - So I need check for Libraries, netlist, SDC, UPF and DEF.
Checks should be the ones which impact Implementation and are not covered by people who are providing inputs -
i.e. - GCA and 0RC timing - for costraint checking will be executed by person handing over SDC
As an implmentation person, I need to write screener for PnR, capturing/covering anything/everything which will impact my QoR - at the same time making sure I am not repating checks being done by the experts (input providers)
Checks I have thought of are -
-> DEF and netlist consistency (because two different people are providng inputs, which might be clean but may not work togther)
-> Utilization report
-> congestion Map for better predictability - makes more sense if DCT is used for SYnthesis
-> check if all implementation corners are available in libraries
-> Data linking (DEF + netlist + UPF +SDC)
-> Leakage report of netlist - with summary of cells/ICGs/Vt types
-> Summary of clocks -> to check if clocks has required frequency
-> Clock domain crossing report -> to see if case analysis is ok
-> report_qor
Please suggest more checks, quick response is really appreciated. I want checks to be precise with their intent clear. Any checks worth capturing before PnR to ensure quality and completeness of input data is good.