User guide

CoMET Version 5.9 – Tutorial 21
CIF Module - SimpleVSP
Overview
This tutorial demonstrates how to build a Virtual System Prototype (VSP) and simulate it
running target code, using the CoMET System Engineering Environment.
A VSP (Virtual System Prototype) is a constructed from a collection of software projects
made up of source code, compiled modules and xml files. The software runs on a simulation
engine on a host PC, modeling the behavior of a hardware system. You can run target
software developed for the hardware system on the VSP at speeds approaching the speed of
the actual hardware system.
The Virtual System Prototype and its Components
The Virtual System Prototype (VSP) is the top level module. It represents the virtual world in
which simulation takes place. It has no external connections or ports. It contains all other
modules. VSP behavior is determined by the modules it contains. It has no behavior
independently of its modules. A VSP typically contains least one instance of a Virtual
Platform. A VSP is the equivalent of the VHDL test bench.
A Virtual Platform contains instances of other modules, which may include Peripheral
Device models and other Virtual Platforms. It may have ports. Virtual Platform behavior is
determined by the modules it contains. It has no behavior independently of its modules.
A Virtual Processor Model (VPM) models the behavior of a microprocessor. Typically a
VPM is a module within a Virtual Platform. A VPM has ports.
A Peripheral Device model emulates the behavior of physical devices such as interrupt
controllers, clock generators, asynchronous serial interfaces and so on. A Peripheral Device
has ports.
A Net provides a means to connect module instance ports, and is the means by which you
connect devices and platforms in your VSP. You can create clock, logic, vector or bus nets.