editor's blog
Subscribe Now

Describing User-Defined Faults

In today’s article on cell-aware fault modeling, we described how specific layout-dependent faults can be accounted for in the test suite, increasing the test coverage beyond what stuck-at modeling provides and yet keeping the vector count down below what gate-exhaustive modeling would require.

But there has to be some way of defining these specific “user-defined” faults so that the test generation program can include them in the test suite.

Mentor devised their so-called “User-Defined Fault Model”, or UDFM, language to handle this. It’s a human-readable and -writable format, and you can use it to define both static and transition faults. This allows you to describe specific custom faults manually if you wish, although, as described in the article, it would be written out automatically by the tools.

As an example, the following would define the four possible alternative tests for the static fault caused by the low-resistance bridge example in the article:

Fault “Bridge-R4” {

       Test {StaticFault “Z”=0; Condition “S0”=0,”S1”=0,”D0”=0,”D1”=-,”D2”=1}

       Test {StaticFault “Z”=0; Condition “S0”=1,”S1”=0,”D0”=-,”D1”=0,”D2”=1}

       Test {StaticFault “Z”=0; Condition “S0”=0,”S1”=1,”D0”=1,”D1”=-,”D2”=0}

       Test {StaticFault “Z”=0; Condition “S0”=1,”S1”=1,”D0”=-,”D1”=1,”D2”=0}

}

Leave a Reply

featured blogs
Sep 20, 2019
The optical communications world will be centered in Dublin next week for ECOC Exhibition 2019. This is one of “the” events in the fiber optics world. ECOC features over 6,000 attendees and 330 exhibitor from around the globe. The industry will focus on networking...
Sep 20, 2019
Earlier this year, on July 20, we celebrated the 50th anniversary of the first landing on the moon. I wrote about it'€”well, mostly about the Apollo Guidance Computer'€”that day in my post The First... [[ Click on the title to access the full blog on the Cadence Communit...