Posted by Tom De Schutter on December 4, 2015
End-to-end prototyping to the rescue
In this blog I have been discussing the increasing impact of software on many aspects of our lives. In the past we mostly interacted with a software-driven device when we sat in front of a desktop computer. We now carry a device with us that is as powerful as a computer. Our cars track our moves and try to pre-empt an accident by warning us about rapidly approaching obstacles, or prevent our tires from slipping on wet or snow covered roads. In our homes, the thermostat reduces the temperature when it ‘notices’ that there is no longer movement in the house.
It should be no surprise to readers of this blog that I feel strongly about the value of prototyping to pull in the development of software and enable hardware–software co-design. Hardware and software no longer can be seen as two independent deliverables of the same end-product. The software needs to be developed in context of the hardware, and the hardware needs to be designed with the software in mind.
I have dedicated multiple blogs about specific types of prototyping methods to address certain design challenges. While each prototyping method offers a lot of value on its own, it is the combination of prototyping solutions that helps maximize the shift left of the design development. The result is much better products that can be delivered faster.
This is where an end-to-end prototyping strategy really pays off. As part of an electronics device design, you need to take care of the architecture design, software development and testing, hardware/software integration and system validation. All of these tasks rely heavily on software scenarios and hence all of them benefit from deploying prototyping.
In a recent webinar I talked with Chris Rommel, executive vice president of IoT & embedded technology at VDC Research, about some of the challenges originating from the ever-growing software content and complexity and the value of end-to-end prototyping as a solution to address these challenges. Chris explained how VDC’s research shows that software is now the largest single center of investment for electronics products and engineering challenges such as application complexity, technical obstacles and changes in the specifications are causing project delays. VDC’s research also showed a growing adoption of prototyping methods to address these schedule delays. VDC indicated that the trend toward end-to-end prototyping is driven by a need to get the software right in context of the hardware, and perform hardware-software co-design early on to address the growing complexity of software.
In the second half of the webinar, I explain Synopsys’ view on end-to-end prototyping. The mains goals are:
• Get the SoC architecture right.
• Achieve the shortest time to quality software.
• Reduced the schedule risk with pre-silicon software bring-up.
• Validate the hardware and software early on in context of real world conditions.
End-to-end prototyping is more than the sum of the individual prototyping solutions put together. Leveraging models, software and real world I/O interfaces across the development spectrum provides unique value links that boost the overall productivity by more than just time-to-market, but also in better product design where software and hardware work together in harmony rather than being overlay pieces of each other. To touch on a couple of these value links:
• By developing software early using virtual prototypes, SoC-ready software can be used to pull in hardware-software integration, enabling an early feedback loop for both hardware and software.
• Virtual prototyping power models used for early power/performance analysis of the SoC can be leveraged for development and testing of the power management software.
• Virtual, physical or hybrid prototypes running software can be used to capture workloads from a current project and leveraged as benchmarks for designing the next generation SoC architecture.
• Hybrid prototypes, combining virtual and physical prototypes, leverage the virtual prototype to run the OS on the next-generation application subsystem and develop IP-specific software in context of real world conditions for interface IP mapped onto the FPGA.
A more elaborate overview of end-to-end prototyping can be found in this white paper.
The electronics revolution can both be promising and daunting. If you are or want to be part of it, I recommend you to watch the webinar and/or read the white paper to see how end-to-end prototyping can help you embrace the growing influence of software.
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.