Scribd
Upload
25 views3 pages

Why Do I Get Additional DRC Violations When I Enable Pipelined Scan Data

Enabling the pipelined scan data feature in design tools like DFT Compiler and TetraMAX can lead to additional expected DRC violations due to the interaction with other DFT features. A table outlines specific DRC warnings associated with various scan types and configurations. Understanding these warnings is crucial for effective DRC analysis and troubleshooting in design flows.

Uploaded by

xylcool5
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
25 views3 pages

Why Do I Get Additional DRC Violations When I Enable Pipelined Scan Data

Enabling the pipelined scan data feature in design tools like DFT Compiler and TetraMAX can lead to additional expected DRC violations due to the interaction with other DFT features. A table outlines specific DRC warnings associated with various scan types and configurations. Understanding these warnings is crucial for effective DRC analysis and troubleshooting in design flows.

Uploaded by

xylcool5
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

(/s/) Cases (/s/case-list) STARs (/s/star-list) Articles (/s/knowledge) Help (/s/help-info)

Dec 11, 2019 • Knowledge

Title
Why Do I Get Additional DRC Violations When I Enable Pipelined Scan Data?

Description
Question:

I enabled the pipelined scan data feature in my design, and now I see additional DRC violations in my DFT Compiler and TetraMAX runs. Is
this expected?

Answer:

Yes, certain additional DRC violation warnings are expected when you enable the pipelined scan data feature. They depend on which
other DFT features you are using in your flow. The following table summarizes these additional expected DRC warnings for post-DFT DRC
in Design Compiler and DRC in TetraMAX. State-holding head pipeline registers are used for all configurations.

Expected Additional DRC Violation Warnings from Scan Data Pipelining

Tool Scan Type Pipeline Registers? C15 C16 R14 S19 S22 V14

DFT Compiler std none

DFT Compiler comp none

DFT Compiler std same clock as scan

DFT Compiler comp same clock as scan X

DFT Compiler std dedicated pipeline clock X X

DFT Compiler comp dedicated pipeline clock X X X

TetraMAX std none

TetraMAX comp none

TetraMAX std same clock as scan X

TetraMAX comp same clock as scan X X

TetraMAX std dedicated pipeline clock X X

TetraMAX comp dedicated pipeline clock X X X

These DRC warnings are as follows:


C15 - scan cell port unable to capture
(https://solvnet.synopsys.com/dow_retrieve/latest/tmax/tmax_olh/Content/man_drc_c15.htm)
C16 - nonscan cell port unable to capture
(https://solvnet.synopsys.com/dow_retrieve/latest/tmax/tmax_olh/Content/man_drc_c16.htm)
R14 - X source T gate (G1) is propagatable to N scancells.
(https://solvnet.synopsys.com/dow_retrieve/latest/tmax/tmax_olh/Content/man_drc_r14.htm)
S19 - nonscan cell disturb (https://solvnet.synopsys.com/dow_retrieve/latest/tmax/tmax_olh/Content/man_drc_s19.htm)
S22 - multiple clocked scan chain (https://solvnet.synopsys.com/dow_retrieve/latest/tmax/tmax_olh/Content/man_drc_s22.htm)
V14 - missing state (https://solvnet.synopsys.com/dow_retrieve/latest/tmax/tmax_olh/Content/man_drc_v14.htm)

These additional DRC violations sometimes occur because the DRC analysis process can vary depending on the DFT features used. For
example, S22 occurs in standard scan mode because the entire scan chain from scan-in to scan-out is analyzed together. However, in
scan compression modes, DRC is performed separately for the compressed scan chains and for the paths between the scan-ins and
scan-outs and the decompressor and compressor, respectively.

Workaround

Product L1
TestMAX DFT (/s/detail/01t1U000003IXzUQAW)

Additional Product(s)
TestMAX ATPG (80003968)

Article Number
000018937

Last Published Date


12/11/2019, 12:54 PM

Article Record Type


How To

URL Name
Why-Do-I-Get-Additional-DRC-Violations-When-I-Enable-Pipelined-Scan-Data-1576092571344

Was this article helpful? 0 1

Recommended Articles

Why Do I Get an S1 DRC Violation in wrp_of Mode When Using an OCC Pipeline Clock?

Why Do I Get S1 DRC Violations at Synchronous Set/Reset Scan Cells?

DRC Violations Reported on Scan Segments When Using the preview_dft Command in a HASS Flow

Why Am I Getting D14 and C6 Violations During Test DRC?

Why Do I Get TEST-126 Messages During dft_drc?

Related Files (0)


Article Comments (0) (/s/relatedlist/ka01U000001dnjvQAA/Article_Comments__r) New

Saved Articles (0) (/s/relatedlist/ka01U000001dnjvQAA/Saved_Articles__r) New

You might also like