Basics of hardware/firmware interface codesign
Gary Stringham
Embedded.com (July 7, 2013)
Hardware and firmware engineering design teams often run into problems and conflicts when trying to work together. They come from different development environments, have different tool sets and use different terminology. Often they are in different locations within the same company or work for different companies.
The two teams have to work together, but often have conflicting differences in procedures and methods. Since their resulting hardware and firmware work have to integrate successfully to build a product, it is imperative that the hardware/firmware interface – including people, technical disciplines, tools and technology – be designed properly
This article provides seven principles hardware/firmware codesign that if followed will ensure that such collaborations are a success. They are:
- Collaborate on the Design;
- Set and Adhere to Standards;
- Balance the Load;
- Design for Compatibility;
- Anticipate the Impacts;
- Design for Contingencies; and
- Plan Ahead.
E-mail This Article | Printer-Friendly Page |
Related Articles
- Tips for doing effective hardware/firmware codesign: Part 2
- Tips for doing effective hardware/firmware codesign
- Basics of the Cortex MCU Software Interface Standard: Part 1 - CMSIS Specification
- HW/SW Interface Generation Flow Based on Abstract Models of System Applications and Hardware Architectures
- The basics of setting up hardware verification testbenches using OVM configuration classes