Turnkey UWB MAC and PHY platform IP, for FiRa 2.0, CCC Digital Key 3.0, and Radar
How to make virtual prototyping better than designing with hardware: Part 2
The importance of testability in virtual prototyping
By Everett Lumpkin and Casey Alford
Embedded.com (06/23/10, 12:15:00 AM EDT)
Virtual prototypes are much more conducive to design automation because the environmental stimulus is just another component of the simulation. Careful control of the stimuli results in deterministic behavior of the product simulation.
Sometimes tool integrations are still required (for example a debugger, Matlab or LabView), but complexity is reduced to the exchange of information via control APIs and configuration files rather than cables, networks, and manual setup of test panels.
Users of VP prototypes are able to automate the testing process via software scripts eliminating the need for custom equipment and cables. Flash memory is simply loaded with a program image rather than re-flashed with complicated tools on the real hardware. Finally, the virtual prototype is truly time share-able as each user can have their custom configuration without fear of breaking anothers test setup.
![]() |
E-mail This Article | ![]() |
![]() |
Printer-Friendly Page |
Related Articles
- How to make virtual prototyping better than designing with hardware: Part 1
- How to make virtual prototyping better than designing with hardware: Part 1
- Dealing with automotive software complexity with virtual prototyping - Part 2: An AUTOSAR use case
- How to use UML in your SoC hardware/software design: Part 2
- Designing optimal wireless base station MIMO antennae: Part 2 - A maximum likelihood receiver
New Articles
- MIPI in FPGAs for mobile-influenced devices
- Optimizing 16-Bit Unsigned Multipliers with Reversible Logic Gates for an Enhanced Performance
- How NoC architecture solves MCU design challenges
- Automating Hardware-Software Consistency in Complex SoCs
- Beyond Limits: Unleashing the 10.7 Gbps LPDDR5X Subsystem