You copied the Doc URL to your clipboard.

PVBusMapper component

This section describes the PVBusMapper component.

PVBusMapper - about

This component is a general purpose modeling component.

It performs like PVBusModifier, but it also has multiple downstream ports, allows routing of transactions to any one of these ports, and allows arbitrary remapping of transaction addresses and attributes.

As a generic device, it does not have a hardware revision code.

PVBusMapper - ports

This section describes the ports.

Table 4-200 PVBusMapper ports

Name Protocol Type Description
control PVBusMapperControl Master Control port for configuring the routing and mapping behavior.
pvbus_m[64] PVBus Master Bus master ports.
pvbus_s PVBus Slave Bus slave port.
reset Signal Slave Reset signal.

PVBusMapper - parameters

This section describes the parameters.

Table 4-201 PVBusMapper parameters

Name Type Allowed values Default value Description
handling_of_dvm_messages_from_downstream string forward, handle, terminate forward What to do with Distributed Virtual Memory (DVM) messages from downstream. The options are to 'forward' them upstream unaltered, to 'terminate' them, or to 'handle' them locally with handleDownstreamDVMMessage(). This parameter is not a runtime parameter.
handling_of_dvm_messages_from_upstream string forward, handle, terminate forward What to do with Distributed Virtual Memory (DVM) messages from upstream. The options are to 'forward' them downstream unaltered, to 'terminate' them, or to 'handle' them locally with handleUpstreamDVMMessage(). This parameter is not a runtime parameter.
handling_of_upstream_snoop_requests string forward, handle, terminate forward What to do with snoop requests from downstream. The options are to 'forward', 'terminate' or 'handle'. The snoop request addresses are not translated: if your device alters the address translation then you almost certainly want to 'terminate'. This parameter is not a runtime parameter.
Was this page helpful? Yes No