Visible to Intel only — GUID: group__group__compiler__mem__axi4__driver_1gae8e607c0391a1670cca0a5242818b05b
Ixiasoft
Visible to Intel only — GUID: group__group__compiler__mem__axi4__driver_1gae8e607c0391a1670cca0a5242818b05b
Ixiasoft
5.2.2.21. write_cmd
Usage
def pyhydra.ipkits.hydra.driver_mem_axi4.driver_compiler.MemAxi4Driver.write_cmd (cls, iters, awvalid, wvalid, bready, awid, workers)
Description
Configure the AXI write traffic stream.
This API controls the write traffic stream: generating commands on the AW and W channels, and monitoring responses on the B channel. Multiple "workers" can be configured, each controlling a distinct traffic stream for every unique AWID, and the workers are multiplexed onto the AXI bus. This API waits for all the AW and W channel commands to be generated but does not wait for the B channel responses to return.
Parameters
- iters
-
Number of AXI write commands to generate. Max iters is 65,536.
- awvalid
-
AWVALID waveform specified as a tuple representing pulse-width-modulation: (on_cycles, total_cycles). Unit is in clock cycles, max total_cycles is 8.
- wvalid
-
WVALID waveform specified as a tuple representing pulse-width-modulation: (on_cycles, total_cycles). Unit is in clock cycles, max total_cycles is 8.
- bready
-
BREADY waveform specified as a tuple representing pulse-width-modulation: (on_cycles, total_cycles). Unit is in clock cycles, max total_cycles is 64.
- awid
-
Worker execution sequence specified as a list of their AWIDs.
- workers
-
List of worker objects (write_worker_op). Every worker in this list must have a unique AWID.
Returns
Compiler IR object