Scribd
Upload
186 views

Coverage Improvement: by Deepa.B

The document discusses improving coverage for an Intel project from 99.32% stuck-at coverage to over 95% at-speed coverage. This was achieved by addressing issues including feedback loops, blocking, abort limits, lack of observability, and tool version.

Uploaded by

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

Coverage Improvement: by Deepa.B

The document discusses improving coverage for an Intel project from 99.32% stuck-at coverage to over 95% at-speed coverage. This was achieved by addressing issues including feedback loops, blocking, abort limits, lack of observability, and tool version.

Uploaded by

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

Coverage improvement

By Deepa.B
Intel Project
• Total number of blocks are 5.
– par_iom
– par_tbt_dp
– par_tbt_dma
– par_psftc_top
– par_psftc4
par_tbt_dma 

• Stuck@ coverage was 99.32%


• Whereas in At speed only 93.67% was
achieved but requirement 95.00%.

 
Coverage improvement
• To increase 1.43% coverage in At speed.
• By Analysis there was
1. Feedback loop issue
2. Blocking issue
3. Abort issue
4. Less Observabilty (cut point)
5. Tool issue(old version)
Feedback
• There was more feedback circuit as show
below
• Where syn 34 output – syn 36 input – syn 34
input .
• It mean that syn 34 input was controlled by
syn output
Blocking (BL)
• In a figure one of the AND gate input
connected to ground.
• Due to that another input of AND gate fault
will not detect.
• By observing below figure it contain 6 fault.
Abort
• But increasing abort limit we get coverage on
UC and UO in between two scan flop.
Loss observability
• By adding cut point at memory output we are
getting detect fault(DS) till syn 38 output.
• From syn 38 to syn 39 we are getting UO.AAB
fault at input of syn 39.
• To get observabilty from Syn 39 we added cut
point at output of syn 39.
• This cut point are verified and added as test
point by scan team.
TOOL issue
• Tool issue as show in below figure where syn
21 output fault was detected but at syn 22
input fault was showing as ( AU AAB/AU AAB)
It mean its not detected.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy