Special Appendix
Use of Nemesis

In general fault dictionaries can be made any number of ways: by hand, through simulation, or from a tester machine. Sproing is set up to read Nemesis generated fault dictionaries. So any input to Sproing has to be in this specific format (as described in the File Descriptions: Pre-Input file section). Ideally one would feed Sproing tester data, and a composite bridging fault dictionary. A composite bridging fault dictionary usually consists of information from both stuck-at signatures, and information from a bridgeIDDQ dictionary. The IDDQ dictionary is not required, a simple stuck-at dictionary will work fine, but more restricted vectors (see match restriction) are identified through the IDDQ tests.

Up next are examples of stuck-at, bridgeIDDQ, and bridge fault configuration files for Nemesis. But there is a slight conundrum, these files, and the options needed to get Nemesis to generate them, arenít in any official Nemesis documentation. The documentation that exists is useful, and explains much about Nemesis, and itís file formats, in general [3].

Running Nemesis is easy:

% Nemesis c432

or whatever circuit you wish to diagnose. Do this with separate configuration files for each type of dictionary, and youíre done. This creates the necessary .dictionary files that will need to be converted into .ddb format. The hard part is creating the configuration files. In the next few pages are a few sample configuration files that have been used to create appropriate dictionaries

Nemesis.config files for:
Stuck-at fault dictionary creation
BridgeIDDQ fault dictionary creation
Bridge fault dictionary creation