Posted by Marc Serughetti on July 25, 2009
For people interested in electronic system virtualization, the term virtualization itself may be confusing. There is indeed a lot of different use for the term virtualization. The most well-known one being of course the one made famous by the IT community and companies such as VMWare. As to clarify some of the discussion on this blog, let me define what we mean by Electronic System Virtualization.
We have to consider two elements “Electronic System” and “Virtualization”: “Electronic System” refers to electronic products ranging from processor core and chip to hardware boards, devices (for example a mobile phone, a printer, a router, a medical device, …) and even network of devices (for example a car with a network of ECU). As a result “Electronic System Virtualization” is the emulation/simulation of such electronic systems. It should be noted that how the electronic system is virtualized depends on the use one would have to the virtualization technology. For example one could imagine a virtualization enabling interconnect and memory performance optimization where the interconnect and memory subsystem of the hardware will be represented with a high level of accuracy while traffic generators are used as the electronic system test environment. Another one could imagine a virtualization enabling the development of software, which would define the virtualization as a view of the hardware relevant from a programmer’s perspective only. There are many use cases for Electronic System Virtualization and each use may have specific requirement with regard on how it needs to be virtualized.
So why should you care about electronic system virtualization? Electronic systems complexity is increasing. The costs for defining, developing and deploying such systems have increased significantly. Companies need to have the system right the first time while reducing costs and enabling their go-to-market. “Electronic System Virtualization” provides the infrastructure (tools and methodologies) to address these challenges.
Do you have experience with “Electronic System Virtualization”. Let us know what you think.
Patrick Sheridan is responsible for Synopsys' system-level solution for virtual prototyping. In addition to his responsibilities at Synopsys, from 2005 through 2011 he served as the Executive Director of the Open SystemC Initiative (now part of the Accellera Systems Initiative). Mr. Sheridan has 30 years of experience in the marketing and business development of high technology hardware and software products for Silicon Valley companies.
Malte Doerper is responsible for driving the software oriented virtual prototyping business at Synopsys. Today he is based in Mountain View, California. Malte also spent over 7 years in Tokyo, Japan, where he led the customer facing program management practice for the Synopsys system-level products. Malte has over 12 years’ experiences in all aspects of system-level design ranging from research, engineering, product management and business development. Malte joined Synopsys through the CoWare acquisition, before CoWare he worked as researcher at the Institute for Integrated Signal Processing Systems at the Aachen University of Technology, Germany.
Tom De Schutter
Tom De Schutter is responsible for driving the physical prototyping business at Synopsys. He joined Synopsys through the acquisition of CoWare where he was the product marketing manager for transaction-level models. Tom has over 10 years of experience in system-level design through different marketing and engineering roles. Before joining the marketing team he led the transaction-level modeling team at CoWare.