There are three main components of the -VP: Free Open Source model, simulator OVPsim, Modeling API.
With these components, it is very easy to put together advanced multi-core platforms with heterogeneous or homogeneous complex hierarchies of memory, the cache systems and layers of embedded software - operating at 100s of MIPS on the desktop standard.
In the downloads of many examples of components and complete platforms - these are added all the time. For example, you can download a simple example of a platform-MIPS32 4KEm as source or executable, download a program such as the Dhrystone benchmark as source or executable, download the appropriate MIPS toolchain compile and debug - and in some minutes - to get it running on your Windows PC own try - experience for yourself a software platform powered virtual 300MIPS feels like ... Download now ... reach the new world of embedded software development using OVP.
Get your grade
or your money back
using our Essay Writing Service!
If you have questions regarding OVP technology, please visit the forums for information.
If you are interested in using technology with OVP OSCI SystemC then please visit the page or page TLM2.0 SystemC SystemC.
If you are interested in using technology with OVP SPIRIT Consortium IP-XACT and SystemRDL then please visit the SPIRIT.
If you have a bug or other issue please visit the forum to raise the issue and in the control trial than others have not already been answered the same question.
Open Source models (more)
In OVP, there are several different types of models. These models are provided both as pre-compiled object code, and as source files. Currently, there are models of treatment of ARC, ARM, MIPS, and families OpenRisc. There will be other families in a timely manner. There are also models of various types of system components, including RAM, ROM, trap, cover, bridge, etc. There are also models of peripherals, including DMA, UART, FIFO, etc. There are also several models different platforms pre-built, including software as ucLinux to run on them. Currently, the models are hosted on this site OVP, if it intends to move these timely source forge. When they move to Source Forge, we will strive to maintain the binary models on this site. Please visit the download area model with updated lists and download.
simulator OVPsim (more)
A fast simulator - OVPsim is provided in the download area. OVPsim is now released on Windows XP SP2 and Linux FC4. OVPsim provides simulation capabilities to launch platforms and processors OVP models of devices at fast speeds fiercely - please download an example experienced how fast virtual platforms software can work with OVP . A 32-bit RISC processor type will boot an operating system to 2-300MIPS on a desktop PC. top speeds of up to 1200MIPS have been experienced ...
OVPsim is a Just-In-Time Code Morphing (in binary) of the simulation engine which dynamically translates instructions to x86 instructions target host. OVPsim has been specifically architected for the fastest speed of simulation and includes numerous optimizations for simulation platforms using the number of homogeneous and heterogeneous processors with many complex memory hierarchies. OVPsim includes modeling very effective MMU / TLB.
Platforms over 1000 processors were simulated efficiently on desktop computers.
For more information please visit the area OVPsim the downloads area for a detailed explanation.
OVPsim can be wrapped and called from other simulation environments and comes standard with wrappers for C, C + + and SystemC.
Another key technology is that it can encapsulate OVPsim existing models of processors and binary models. It was therefore easy to use legacy processor models in a simulation OVP. (Of course, the overall speed of the simulation can be limited by the speed of these models encapsulated.)
OVPsim comes with a GDB RSP interface and is easy to use with standard debuggers support this interface GDB RSP.
Modeling API (more)
In OVP models are created by writing code calling functions in a specific modeling API. These APIs are based on C and are normally used with C, there are models available for use with C + + and SystemC.
To model an embedded system, there are several key points to model: platforms, processors, devices and the environment. The platform connects and configures the purely behavioral components. Processors seek and execute object code instructions from memory and peripheral components of the model and the environment than the operating system and application software interacts with.
Always on Time
Marked to Standard
Modeling OVP includes several APIs, ICM VMI, BHM / MPC.
In the area of the downloads are very complete reference documentation, application notes, documents online, the file header and sample all the different functions in each API. Please consult these documents to see the full explanation and reference.
For platforms there CIM API for controlling, logging, and observing platforms. This API can be called from C, C + + or SystemC. The platform provides the basic structure of the design and creates, connects, and configures the components. The platform also provides the address mapping, and software that is loaded on the processors. It is very easy with ICM to specify very complex and full of many different platforms, processors, local memories and shared caches, bridges, bus, peripherals, and all their cards solve complex problems, outages and systems operating and application software.
For modeling the processor is the VMI API. The API functions are called from your C code and offer the opportunity to easily describe the behavior of the processor. A processor model written in C using the IMV essentially decodes the instruction to simulate target, this translates x86 instructions, which are then executed on the PC. IMV can be used to model 8, 16, 32 and 64 bit architectures and Extensions for VLIW DSP, etc. It is a mechanism for trapping intercept calls to functions in libraries execution of applications such as printf, without requiring modification of the processor models.
PPM and BHM (more)
behavioral components, peripherals, and the global environment is modeled using the C code and calls to these APIs. Underlying these API is an event-based planning mechanism to allow the modeling of time, events, and competition - it is normally very easy to model the functionality of the components of embedded systems. peripheral models provide reminders that are called when the application software running on processors modeled in places platform memory when the device is activated. These APIs enable extremely efficient modeling capabilities behavior.