Visible to Intel only — GUID: group__group__compiler__mem__axi4__driver
Ixiasoft
Visible to Intel only — GUID: group__group__compiler__mem__axi4__driver
Ixiasoft
5.2.2. Memory AXI4 Driver APIs
APIs to describe a traffic program for Memory AXI4 Driver.
Detailed Description
-
write_cmd
-
read_cmd
-
wait_writes_cmd
-
wait_reads_cmd
-
loop_cmd
-
parallel_cmd
-
driver_post_cmd
-
driver_wait_cmd
The remaining APIs provided by this compiler are constituents of the above commands.
APIs return the Compiler Intermediate Representation (IR) objects which the compiler can interpret.
Creating a traffic program is agnostic to the driver configuration. However, compiling the traffic program depends on the driver configuration. You must regenerate the compiled binary of the traffic program for each release because it is not portable. You must also regenerate the compiled binary of the traffic program if the configuration of the Test Engine IP has changed because the old binary will no longer be compatible with the new configuration.
The compiler only checks if the hardware can execute the traffic program. The compiler does not check for AXI compliance (example: the burst transfer remain within a 4kB boundary) or if the AXI pattern is well-structured (example: the expected read data match the written data). This behaviour enables negative testing to evaluate how a responder handles unexpected AXI traffic patterns.
Section Content
dq_alu_echo_op
dq_alu_invert_op
dq_alu_rotate_op
dq_alu_prbs_op
data_eq_dq_op
data_eq_raw_op
data_eq_addr_op
data_eq_id_op
dm_alu_echo_op
dm_alu_invert_op
dm_alu_rotate_op
dm_alu_prbs_op
strb_eq_dm_op
strb_eq_raw_op
addr_alu_echo_op
addr_alu_incr_op
addr_alu_rand_op
addr_op
write_worker_op
read_worker_op
write_cmd
read_cmd
wait_writes_cmd
wait_reads_cmd
sleep_cmd
driver_post_cmd
driver_wait_cmd
parallel_cmd
loop_cmd