Tips for doing effective hardware/firmware codesign: Part 2

By Gary Stringham, Gary Stringham & Associates, LLC
Embedded.com (September 17, 2013)

A success factor of embedded systems products is its performance. Is it fast enough to meet the customer’s requirements and expectations? But is it cheap enough that the customer will buy it? Putting a V-8 engine on a lawn mower will definitely provide sufficient performance; however, it will be too expensive for the consumer. Performance must be weighed against cost.

Previously discussed in Part 1 were tradeoffs between polling a status bit and waiting for an interrupt. Interrupts allow firmware to work on something else until the event occurs, and then be notified immediately when it does occur.

But judicious use of interrupts is required to avoid bogging down the system with interrupts occurring too frequently. Likewise, other aspects of the hardware/firmware interaction require judicious designs to ensure optimal performance.

This section discusses a few techniques to maximize the performance at the hardware/firmware interface without incurring too much cost in the platform.

To read the full article, click here