|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Hardware Software
Co-Design/Verification, Part I - HW SW Modeling
As advancements in ASIC design methods and EDA tools revolutionize chip design, new embedded IP and system design techniques revolutionize both system and chip design. Embedding processor and DSP cores within chips with major software functions calls for system level tools for system and chip architecture development, HW SW tradeoff analysis, and System-On-Chip design implementation. System designers have used instruction set simulators and high level modeling languages, particularly C, for many years. Several commercial companies have developed proprietary languages and simulation or modeling products to support their languages. In this article you will see a dialog of whether C should be the language of choice for HW SW Co-design or whether a new bridge language for HW SW definition is a better solution.
EDA tool companies are racing to meet the opportunity for new tool solutions. The 1999 Design Automation conference was alive with advancements in EDA products for system level design with a substantial presence of both established and start-up EDA companies willing to show their capabilities. We provide a matrix of companies, their products, and tool functions shown at DAC, and a glimpse at how representatives and experts from EDA companies expect that the industry will meet the need for improvements in HW SW Co-Design/Verification.
Experts of representative companies were asked to share their vision for HW SW Co-Design/Verification a few years into the future. This is what they had to say.
"System designers are realizing that in order to adopt an effective HW/SW system design methodology a new set of tools are required that can utilize abstract system specifications. Tying the specification to design implementation is the key to solving the "system in silicon" problems of design reuse, early access to virtual prototypes for software development and automated transformation from specification to hardware and software. Over the next two years, design creation, analysis, verification and synthesis tools will become available and mature enough to support high level system design and the methodology necessary for improving HW/SW co-development productivity."
Charlie Loegering, VP New Business Development, Summit Design Automation
"Successful companies will be designing at the system level, supported by an increasingly automated RTL implementation flow. Interface synthesis will make plug-and-play IP a reality. The hardware and software teams will be tightly integrated, using C/C++ as a common design language. Early hardware-software integration will eliminate the current system verification bottleneck."
Nick Lethaby, Technical Marketing Manager, CoWare, Inc.
"As for the future of HW/SW design, I believe that to enable true co-design between hardware and software teams, it is imperative to have both groups using the same language. It is the only way to facilitate rapid design iterations between the two groups. By supporting ANSI C which is the universal language used by software developers, hardware designers now have a common design language to work with
software developers that also links seamlessly with their existing RTL design flows."
David Park, Vice President, Marketing, C Level Design, Inc.
"With the advent of the embedded processor and System-On-Chip (SOC), HW/SW co-design has become a mandatory part of the design flow. This need is driving a change in methodology, for which the only solution can be a design language capable of supporting architectural, HW and SW design together. True SOC requires the cooperation of different design specialization's, and they must all be talking the same language for success."
David Kelf, Vice President, Worldwide Marketing, Co-Design Automation
"In two years hardware/software co-design will be a necessity, but it will be merely part of the solution. Co-design must be combined with co-verification, simulation, architectural assessment, realization and specification. In short, a systems engineering methodology, fully integrated from start to finish, is needed to successfully address increasing chip complexity and shrinking market windows."
Dr. Graham Hellestrand, Chief Executive Officer, VaST Systems Technology
"The drive toward systems on a chip (SOC) designs is forcing developers and suppliers to view software as an equal partner with hardware in the design. This will require a transition toward higher levels of abstraction in the design process and a marriage of hardware and software at all levels of the design and verification process.
The resulting methodology and process flow will encompass high-level system design, partitioning, code generation, and handoffs to hardware and software design teams. These teams will then need to continue the HW/SW methodology down through detailed functional and timing verification. The flow will allow for continuous, contiguous design and verification at all stages of the design. This could be called the "early and often" co-design/verification flow."
Ellie Burns, Eaglei Product Marketing Manager, Synopsys
Copyright Summit Innovation Inc, 1999
Workstations and Design Tools Archive
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Copyright © 2003 ChipCenter-QuestLink About ChipCenter-Questlink |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||