Software to AXI4-Stream

R2026b

Stream AXI4 data from software to FPGA

Since R2022b

expand all in page
  • Software to AXI4-Stream block

Libraries:
SoC Blockset for AMD / SoC System Simulation / Memory
HDL Coder / SoC System Simulation / Memory

Description

The Software to AXI4-Stream block models a connection between hardware logic and a software task through external memory. The writer (processor) streams data into the channel through a DMA driver using a MathWorks® simplified AXI stream protocol. The block models the datapath and software stack of that connection, including a FIFO, DMA engine, interconnect and external memory, interrupts, kernel buffer management of the DMA driver, and data transfers from the software task.

This block is equivalent to a Memory Channel block with the Channel type parameter set to Software to AXI4-Stream via DMA connected to a Memory Controller block.

Memory Channel block connected to a Memory Controller block, replaced by a Software to AXI4-Stream block

Since the memory controller is implicit to the design - you can instantiate several memory blocks that connect to the same memory unit via a memory controller. Valid blocks are:

The maximum number of manager interfaces in a model is 16.

For more information about the MathWorks simplified AXI stream protocol, see AXI4-Stream Interface (SoC Blockset).

This image is a conceptual view of the block, streaming data from a processor algorithm to an FPGA algorithm.

Conceptual view of this block, streaming data from a processor algorithm, through a DMA driver, to memory. Then, the FPGA algorithm reads the data stream.

Examples

Streaming Data from Software to Hardware Using AMD SoC Devices

Streaming Data from Software to Hardware Using AMD SoC Devices

Design the data-path from an embedded processor to hardware logic (FPGA) using SoC builder workflow. Design and simulate the entire application comprising of FPGA and processor algorithms, memory interface, and task scheduling to meet the system requirements. Then, validate the design on hardware by generating code from the model and implementing it on a System-on-Chip (SoC) device.

(SoC Blockset)

Ports

Input

expand all

This signal contains the data sent from the processor to the algorithm.

Data Types: SoCData

This port accepts a control bus from a data consumer block, signaling that the consumer block is ready to accept read data. The rdCtrlIn port is a backpressure signal from a data consumer to the Software to AXI4-Stream block. To create this control bus, use the SoC Bus Creator (SoC Blockset) block.

Data Types: StreamS2MBusObj

Output

expand all

This signal contains the data read from the processor through the memory.

Data Types: single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point

This signal represents the protocol bus from the memory channel to the data consumer. Connect this signal to the data consumer. To separate the signal from the control bus, use the SoC Bus Selector (SoC Blockset) block.

Data Types: StreamM2SBusObj

This port sends a task event signal that triggers the Task Manager (SoC Blockset) block to execute the associated event-driven write.

Data Types: rteEvent

This message port sends a notification to the connected Stream Write (SoC Blockset) block. This notification indicates that a read transaction completed, and that a buffer in memory is available for writing.

Data Types: Boolean

Parameters

expand all

Memory simulation provides three levels of timing resolution. Select one of these options:

  • Burst accurate — Simulates memory contention and high-resolution timing.

  • Protocol accurate — Simulates AXI4 protocol hand-shaking sequencing and low-resolution timing.

  • Behavioral — Simulates data transactions only and no timing.

    When this parameter is set to Behavioral mode, the value of the TLAST signal is ignored.

Tip

To enable performance logging, set this parameter to Burst accurate. Use the Performance Report (SoC Blockset) to display performance metrics.

Main

Choose between processing subsystem (PS) or programming logic (PL) memory.

  • If the selected board supports only PL memory, then the default value is PL memory.

  • If the selected board supports only PS memory or only PL memory, then this parameter is read-only.

  • If the selected board is not a supported SoC board, then this parameter is not visible.

This parameter is read-only.

The size of the region in bytes. This value is calculated as the number of buffers multiplied by the size of the buffer. The size of the buffer is defined as the size of the data multiplied by the software frame size. Define this value by setting the Data type and Dimensions parameters on the Signal Attributes tab.

Example: A software frame size of 1024 uint32 defines a buffer of 4096 Bytes. If the number of buffers is set to 2, the region size is 8192 bytes.

Define the number of buffers in the memory.

The memory access has a ring-buffer pattern. The writer can continually write as long as buffers are available. When a buffer is completed, it becomes available for the reader. The writer and reader traverse the buffers in a circular pattern. As long as the writer and reader maintain similar rates, the buffering prevents blockage.

A disparate rate between a reader and a writer slows down the faster device. For example, a slow reader causes the writer to run out of buffers and blocks the writer, effectively slowing down the writer to the reader rate. Likewise, a slow writer causes the reader to run out of buffers and blocks the reader, effectively slowing down the reader to the writer rate.

The Number of buffers parameter must be an integer from 3 to 64.

The length of bursts for this connection on the memory bus in units of scalar data. The scalar unit is the packed data type. Specify the burst size for both writer and reader access to the channel.

The channel data is always transferred to the memory model using burst transactions. For the AXI4 configuration, the algorithm logic is responsible for defining the burst through the protocol signals.

The Burst length parameter determines the burst size to the memory, and the rdData signal defines the size of each transfer on the interface.

Specify the depth of the data FIFO, in units of bursts. When the writer has no buffers to write to, the FIFO can absorb data until a buffer becomes available. This value is the maximum number of bursts that the FIFO can buffer before it drops data.

Dependencies

To enable this parameter, select Burst accurate under Memory simulation.

Specify a number that asserts a backpressure signal from the channel to the data source. To avoid dropping data, set a high watermark, allowing the data producer enough time to react to backpressure. This number must be smaller than the FIFO depth.

Dependencies

To enable this parameter, select Burst accurate under Memory simulation.

Specify the frequency of the manager datapath in MHz.

Dependencies

To enable this parameter, select Burst accurate under Memory simulation.

Specify the data width of manager datapath to the interconnect controller in bits.

Dependencies

To enable this parameter, select Burst accurate under Memory simulation.

Signal Attributes

Software data signal

Specify the dimension for the software data (writer) as a whole number.

The default value is 1024.

Specify the data type of the software data (writer). For help, click the ... button and select Data Type Assistant. By default, this value is set to inherit the data type from the source signal.

Stream data signal

rdData can be a multidimensional array. Specify the dimension for the array as a whole number.

Example: 1 — A scalar sample.

Example: [10 1] — A vector of ten scalars.

Example: [1080 1920 3] — A 1080p frame. The frame includes 1080 lines of 1920 pixels per line, and each pixel is represented by three values (for red, green, and blue).

Specify the data type of the rdData port. For help, click the ... button and select Data Type Assistant. By default, this value is set to inherit the data type from the source signal.

Specify a time interval in seconds to define how often the block updates.

When you do not want the output to have a time offset, specify the Sample time parameter as a scalar. To add a time offset to the output, specify the Sample time parameter as a 1-by-2 vector, where the first element is the sampling period and the second element is the offset. For more information about sample times in Simulink®, see Specify Sample Time.

Select this parameter to enable data packing across the last dimension of the signal. The AXI4-Stream to Software block packs the data along the last dimension of the signal. For example, if the channel data type is uint32, the dimensions are [1024 4]. If you select this sample packing parameter, then the memory channel generates 1024 read or write transactions of 128 bits. If you clear this sample packing parameter, the memory channel generates 4096 transactions of 32 bits each.

This figure shows how data is aligned for a signal with data type fixdt10[4x3]. When the data is packed, three 10-bit words are concatenated and extended by 2 bits to a 32-bit word. When the data is not packed, each 10-bit word is extended to a 16-bit word.

The top row shows packed data aligned in samples of 10, 10, 10, and 2 to make 32 bits. The bottom row shows unpacked data aligned in samples of 10 and 6 to make 16 bits.

This figure shows how data is aligned for a signal with data type uint8[8x3]. When the data is packed, three 8-bit words are concatenated and extended by 8 bits to a 32-bit word. When the data is not packed, each 8-bit word is represented as an 8-bit sample.

The top row shows packed data aligned in samples of 8 ,8, 8, and 8 to make 32 bits. The bottom row shows unpacked data aligned in samples of 8 bits.

The combined width of the flattened signal must not exceed 512 bits.

Extended Capabilities

expand all

HDL Code Generation
Generate VHDL, Verilog and SystemVerilog code for FPGA and ASIC designs using HDL Coder™.

Fixed-Point Conversion
Design and simulate fixed-point systems using Fixed-Point Designer™.

Version History

Introduced in R2022b

expand all

See Also

(SoC Blockset) | (SoC Blockset) | (SoC Blockset)

Topics