1.1.1. Altera® AXI4 Memory-Mapped Specification Support
1.1.2. Altera® AXI4 Memory-Mapped BFM Components
1.1.3. Altera® AXI4 Memory-Mapped Supported Features
1.1.4. Altera® AXI4 Memory-Mapped BFM SystemVerilog Packages
1.1.5. Altera® AXI4 Memory-Mapped BFM Supported Flows
1.1.6. Altera® AXI4 Memory-Mapped BFM Supported Simulators
1.3.1. Altera® AXI4 Memory-Mapped Manager BFM Configuration
1.3.2. Altera® AXI4 Memory-Mapped Manager BFM Interface
1.3.3. Altera® AXI4 Memory-Mapped Subordinate BFM Configuration
1.3.4. Altera® AXI4 Memory-Mapped Subordinate BFM Interface
1.3.5. Altera® AXI4-Lite Memory-Mapped Manager BFM Configuration
1.3.6. Altera® AXI4-Lite Memory-Mapped Manager BFM Interface
1.3.7. Altera® AXI4-Lite Memory-Mapped Subordinate BFM Configuration
1.3.8. Altera® AXI4-Lite Memory-Mapped Subordinate BFM Interface
1.3.9. Altera® AXI4 Memory-Mapped Inline Monitor Configuration
1.3.10. Altera® AXI4 Inline Monitor Interface
1.4.1. Using the Altera® AXI4 Memory-Mapped Manager BFM Flow
1.4.2. Using the Altera® AXI4 Memory-Mapped Subordinate BFM Flow
1.4.3. Using the Altera® AXI4 Memory-Mapped Monitor BFM Flow
1.4.4. Altera® AXI4 Memory-Mapped Manager RTL Implementation Example
1.4.5. Altera® AXI4 Memory-Mapped Manager Platform Designer BFM Implementation Example
1.5.1. Altera® AXI4 Memory-Mapped BFM Configuration API
1.5.2. Altera® AXI4 Memory-Mapped BFM Reset API
1.5.3. Altera® AXI4 Memory-Mapped Manager Transaction Creation API
1.5.4. Altera® AXI4 Memory-Mapped Subordinate Transaction Creation API
1.5.5. Altera® AXI4 Memory-Mapped Transaction Configuration API
1.5.6. Altera® AXI4 Memory-Mapped BFM Transaction Execution API
1.5.7. Altera® AXI4 Memory-Mapped Host Memory API
2.5.1.2.1. Class Axi4StreamBytes
2.5.1.2.2. Data Members in Axi4StreamBytes Class
2.5.1.2.3. Methods in Axi4StreamBytes Class
2.5.1.2.4. Class Axi4StreamBytesData
2.5.1.2.5. Methods in Axi4StreamBytesData Class
2.5.1.2.6. Class Axi4StreamBytesPosition
2.5.1.2.7. Methods in Axi4StreamBytesPosition Class
2.5.1.2.8. Class Axi4StreamBytesNull
2.5.1.2.9. Methods in Axi4StreamBytesNull Class
2.5.1.2.10. Class Axi4StreamBytesDataError
2.5.1.2.11. Data Members in Axi4StreamBytesDataError Class
2.5.1.2.12. Methods in Class Axi4StreamBytesDataError
2.5.1.2.13. Class Axi4StreamBytesPositionError
2.5.1.2.14. Data Members in Class Axi4StreamBytesPositionError
2.5.1.2.15. Methods in Class Axi4StreamBytesPositionError
2.5.1.2.16. Class Axi4StreamBytesNullError
2.5.1.2.17. Data Members in Class Axi4StreamBytesNullError
2.5.1.2.18. Methods in Class Axi4StreamBytesNullError
1.2.4.1. Altera® AXI4 Transaction Information
You can set the transaction information by using the following fields in the AlteraAxiTransaction class.
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:
|
burst_type | An enumerated type that specifies the burst types according to the AXI4 specification, as follows:
|
lock | An enumerated type that specifies the atomic characteristics of a transaction. The type of atomic access can be one of the following:
|
prot | An enumerated type that specifies the following privilege, security level, and access type protection attributes of a transaction:
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:
|
rresp | Enumerated type filed that you can use to set a read response , as resp field describes. |