10 - Simulator features and extensions

Summary

The earlier chapters of this book discussed the design and use of a simulator for use in the development of digital electronic systems. The discussion has been widened to include some aspects of testing and design for testability, since application of good practice in these areas leads to better use of costly resources in what is probably the largest part of the design procedure. It is now of value to review the extent to which the aims of simulation can be achieved; to discuss several topics related to the use of simulator; to introduce some enhancements to simulators; and to attempt to look into the future.

Desirable features of a simulator

Some years ago the author wrote down a list of the features he would like to find in a simulator.

1. A simulator is required to give an accurate prediction of the behaviour of a good network.

2. A simulator is required to recognise and give warning of a faulty network.

3. The basic simulator should be independent of technology but recognise the distinctive features of known technologies. Thus devices of any technology might be simulated.

4. The simulator should be capable of handling modes at several levels of abstraction and in the same run (Harding 1989).

5. There is no point in simulating a design in 1 s if it takes a day to diagnose a fault, modify and recompile the network. Hence, associated with the simulator, there must be means to assist the user to find the source of ‘wrong’ results, correct them and recompile quickly. That is, the simulation cycle must be given serious attention (the detail is not within the scope of this book).