Altera® AXI4 Bus Functional Model User Guides

ID 838773
Date 5/19/2025
Public
Document Table of Contents

1.2.4.1. Altera® AXI4 Transaction Information

You can set the transaction information by using the following fields in the AlteraAxiTransaction class.

Table 3.   Altera® AXI4 Transaction Information
AlteraAxiTransaction Field Description
id Specifies the Identification tag for a transaction. This value applies to AWID, ARID, BID, and RID signals, according to the transaction that is created. Refer to AMBA AXI and ACE Protocol Specification, A5-81.
awaddr Specifies the address of the first transfer in a write transaction. It takes the width of the address bus.
burst_len Actual data transfer per transaction is burst_len+1. So, burst_len=0 generates 1 data transfer, burst_len=1, burst_len+1 generates 2 data transfers in a transaction. This value is applied to AWLEN and ARLEN according to the transaction type.
burst_size An enumerated type that specifies the burst sizes according to the AXI4 specification, as follows:
  • AXI4_BYTES_1
  • AXI4_BYTES_2
  • AXI4_BYTES_4
  • AXI4_BYTES_8
  • AXI4_BYTES_16
  • AXI4_BYTES_32
  • AXI4_BYTES_64
  • AXI4_BYTES_128
This value is applied to AWSIZE and ARSIZE, not AxLEN.
burst_type An enumerated type that specifies the burst types according to the AXI4 specification, as follows:
  • BURST_TYPE_FIXED
  • BURST_TYPE_INCR
  • BURST_TYPE_WRAP
  • BURST_TYPE_INVALID (not used as specification allows only three burst types.)
This value is applied to AWBURST and ARBURST according to the transaction type.
lock An enumerated type that specifies the atomic characteristics of a transaction. The type of atomic access can be one of the following:
  • NORMAL
  • EXCLUSIVE
prot An enumerated type that specifies the following privilege, security level, and access type protection attributes of a transaction:
  • NORM_SEC_DATA
  • PRIV_SEC_DATA
  • NORM_NONSEC_DATA
  • PRIV_NONSEC_DATA
  • NORM_SEC_INST
  • PRIV_SEC_INST
  • NORM_NONSEC_INST
  • PRIV_NONSEC_INST

The Altera® AXI4 MM Subordinate BFM host memory implementation does not support protection attributes. However, you can store the data in your own memory and process the data according to the protection attributes. These enumeration strings (and others in the transaction class) use the same or similar names as the Siemens EDA ModelSim* simulator for ease of use and migration. Future releases may use different names for these enumeration strings.

data_words Sets write data for a write transaction. This is an unbounded array using which data for each beat of the burst can be specified. This is driven on WDATA channel in a write transaction and stores the data read from a subordinate on the RDATA channel in case of a read transaction.
wstrb Unbounded array that specifies which byte lane contains valid data. This byte lane width is calculated based on the data bus width.
resp An enumerated type that specifies a write transaction response according to the specification. The Altera® AXI4 MM Subordinate BFM drives the OKAY response for all compliant transactions. You can drive the following different responses, according to the specification:
  • OKAY_RESP
  • EXOKAY_RESP
  • SLVERR_RESP
  • DECERR_RESP
rresp Enumerated type filed that you can use to set a read response , as resp field describes.