3.8.2 LabellerUserSignals

This model is written in LISA+.

LabellerUserSignals contains the following CADI targets:

  • LabellerUserSignals
  • PVBusLogger
  • PVBusMapper

LabellerUserSignals contains the following MTI components:

Table 3-276 Ports

Name Protocol Type Description
pvbus_m PVBus Master Output with modified UserFlags.
pvbus_s PVBus Slave Unmodified input.

Table 3-277 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'.

Table 3-278 Parameters for PVBusLogger

Name Type Default value Description
trace_debug bool 0x0 Enable tracing of debug transactions
trace_snoops bool 0x0 Enable tracing of ACE snoop requests

Table 3-279 Parameters for LabellerUserSignals

Name Type Default value Description
user int 0x0 User signal to be applied to transactions
Non-ConfidentialPDF file icon PDF version100964_1161_00_en
Copyright © 2014–2019 Arm Limited or its affiliates. All rights reserved.