Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Memory in scan testing

Status
Not open for further replies.

raviram80

Member level 3
Member level 3
Joined
Jun 8, 2009
Messages
65
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,288
Activity points
1,750
Hi All,

I know one way of using Memory in scan test is to bypass its outputs using some top level signal. This ensures that we can test memory bist engine flops as well.

I want to know is there any other way of treating Memory besides the above during scan testing?

Please let me know,

Thanks,
 

Some ATPG tools have the capability of actually using the memory during the scan pattern.
 
  • Like
Reactions: hawker

    hawker

    Points: 2
    Helpful Answer Positive Rating
Hi,

If the tool has capability of using Ram in scan test what happens to RAM outputs, because they are X....so could you please elaborate how this is done.

Thanks,

Ravi
 
  • Like
Reactions: hawker

    hawker

    Points: 2
    Helpful Answer Positive Rating
there are many ways to handle the ATPG with memory.

- bypass the memory.
- having Muxes after memory outputs and feed some value to the muxes while testing.
- Design the memory to output deterministic value when certain pin is asserted.
- Initialize the momory before running ATPG.

The first 3 can be achieved by the regualr ATPG tool, but I don't think ATPG tool alone can handle the 4th one. you need a logic to initialize the memory.
 
  • Like
Reactions: hawker

    hawker

    Points: 2
    Helpful Answer Positive Rating
Hi,

RAMBIST is a way to handle testing RAMs inside chips.

Tools automate the process of adding the BIST wrapper around the RAM.

Each RAM configuration will produce a signature that is shifted out of the RAMBIST structure and compared to a known good value.
 
  • Like
Reactions: hawker

    hawker

    Points: 2
    Helpful Answer Positive Rating
I guess you can use some wrapper logic around a memory or analog block for better coverage in scan
 

adding mux around memory, is not really the solution, that create a long path, in functional mode, stop by the memory, in scan not any more, so adding at least one flop during scan, to avoid a long path.
but when you add this logic, you need to test it also in scan. Then you need to find the threshold where the added logic help to find more fault than the logic itself add.

Simplify the ram model, reduce the number of fault, during the std cell scan, and in general, the memories are cover by a software/hardware bist.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top