February 1998, Issue 91

Codesign
The Evolving Relationship Between Hardware and Software

Before taking on a codesign methodology, examine the tools closely to ensure that specific project requirements can be met in the allotted time. Codesign tools should be adopted for smaller projects to give you time to learn the tools before committing the methodology to a critical design project.

A number of things should be considered before committing to codesign. Are the proper models available for the functions required? If not, how will the models be obtained?

What is the cost (in dollars and time) if models must be developed? If models must be developed, will the information be available to develop them?

What developments, if any, are planned by the chip or tool vendor that could aid the design process? What other tools will work with the target codesign toolset?

Codesign toolsets should embody a start-to-finish solution that ideally includes:

• a "real" fully-integrated hardware/software design environment
• software and hardware emulation with programmable breakpoints
• mixed hardware emulation and simulation with visibility at any level
• tool-vendor interface interoperability (a common interface standard)
• high abstraction levels to speed the simulation of large systems
• a flexible, distributed system that allows for multiple design seats
• minimized cost per design seat
• an investment outlay that’s easy to amortize over large production runs
• a portable stand-alone detachable emulation board for system demos
• the ability to keep intellectual property secure for model or chip vendors