Posted by Tom De Schutter on August 30th, 2013
As I am just back from vacation, it is an ideal time to reflect on where we are with virtual prototyping and VDKs (Virtualizer Development Kits). For over a year now we have been developing reference VDKs based on ARM’s Versatile Express board. And it has really made a difference in how we engage with customers. Although we of course always had demos, which were similar to these reference VDKs, having a product quality deliverable that can be used out-of-the-box with software developers makes a big difference. It has helped with the adoption of VDKs at multiple companies across industries and geographies. With only minor additions, or sometimes even no additions, software developers at these customers have been able to bootstrap their device driver, boot code and OS code bring up. On top of that VDKs are helping companies across the supply chain to enable early software development. Semiconductor companies can quickly assemble a VDK for the relevant part of their SoC (depending on the software task) and develop their specific hardware dependent software like e.g. device drivers for all the interface IP of the SoC. System companies can then receive that VDK from their semiconductor vendor and bring up their unique software content without having to wait for board availability. Just recently a company in one part of the world licensed our VDK for ARM big.LITTLE processing. They are in the process of doing some minor customizations to tune the VDK towards their specific SoC. This is possible as they only have to care about the pieces which are relevant for the software that they and their customer want to bring up. Once the relevant drivers are developed and validated, they plan to ship the VDK with their software customization to their systems company customer on the other side of the world. That customer also just licensed our VDK technology to ramp up on the key debug and analysis capabilities that VDKs offer and will be instantly ready to start bring up of their customized OS. By adopting the virtual prototyping methodology and leveraging our reference VDKs these companies are able to significantly accelerate the schedule of their software availability and in the process, improve quality as the software and hardware are tested together before the hardware is completely fixed. This parallel effortresults in the software and hardware being better be tuned for each other.
Simple concepts can lead to big improvements. And what is more logical than starting your software development early by creating a flexible C-model of your design. This recent example of early software development across such distributed geographies shows that more and more companies are coming to this realization.