Peripheral and interface components - about
The Programmer’s View (PV) models show you what the hardware would show you. However, they sacrifice accuracy in timing to achieve fast simulation speeds.
You can test software functionality with PV models, but do not rely
on the accuracy of cycle counts, low-level component interactions, or other hardware-specific
behavior. For example, the AMBAPV2PVBus component rejects transactions with
byte_enable set because PVBus does not support AXI write
The major components are:
- Bus components, including conversions between AMBA and PV model components for use with the SystemC export feature of Fast Models.
- Input/output devices.
- Memory, including flash.
- Ethernet controller.
- Interrupt controllers.
- Static and dynamic memory controllers.
- Audio interface.
- Programmable clock generators.
Some components are software implementations of specific hardware functionality. PrimeCell based components are an example. Other components are necessary as part of the modeling environment and do not represent hardware. Examples of the latter category of component are the bus, clock, telnet, and visualization components.
Components that model specific hardware functionality are either:
- Validated Peripheral Components
- Components that are functionally complete, or have clearly specified limitations. These components can be used to create virtual platforms and have been validated.
- Example Peripheral Components
- Components that have been developed as examples to illustrate ways to model different component types and to enable the creation of specific example virtual platforms. These components can be partially validated.