3.2.7 PVBusMapper

Allow transactions to be remapped arbitrarily. This model is written in C++.

PVBusMapper contains the following CADI targets:

  • PVBusMapper

PVBusMapper contains the following MTI components:

PVBusMapper - about

This component 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 modeling component, it does not have a hardware revision code.

Table 3-49 Ports

Name Protocol Type Description
control PVBusMapperControl Master Configuration port to determine mappings.
pvbus_m[64] PVBus Master Bus master ports.
pvbus_s PVBus Slave Bus slave port.
reset 2.7.2 Signal protocol Slave Reset signal.

Table 3-50 Parameters for PVBusMapper

Name Type Default value Description
pvbusmodifier.handling_of_dvm_messages_from_downstream string "forward" What to do with DVM (Distributed Virtual Memory) messages received from downstream. The options are to 'forward' them upstream unaltered, to 'terminate' them, or to 'handle' them locally and get called through handleDownstreamDVMMessage()
pvbusmodifier.handling_of_dvm_messages_from_upstream string "forward" What to do with DVM (Distributed Virtual Memory) messages received from upstream. The options are to 'forward' them downstream unaltered, to 'terminate' them, or to 'handle' them locally and get called through handleUpstreamDVMMessage()
pvbusmodifier.handling_of_upstream_snoop_requests string "forward" What to do with snoop requests from downstream. The options are to 'forward', 'terminate' or 'handle'. NOTE that currently the snoop request addresses are _not_ translated and so if your device alters the address translation then you will almost certainly want to 'terminate'.
Non-ConfidentialPDF file icon PDF version100964_1161_00_en
Copyright © 2014–2019 Arm Limited or its affiliates. All rights reserved.