Hardware Design Patterns


The purpose of this document is to detail a set of "best practices" solutions to common hardware/software interface design problems.

Systems designed by hardware engineers that do not appreciate the subtleties of interface implementation can impact software development in ways that range cause from anoyances to complete project failures.

Many of the common mistakes impact the ability to write reusable software:

ystems that involve custom hardware with software interfaces

The advent of the micro-processor allows digital hardware designers to avoid a great deal of design effort by plopping down a processor and leaving the problem to the software guys.

The result is inevitably that the

A system development should recognize the needs of both hardware and software aspects systems.

To summarize: get involved with the system design.

The State Change Pattern Interrupt Pattern. describes a best practice for implementing the interface for a set of state change indications.