Test Engine FPGA IP User Guide: Agilex™ 5 and Agilex™ 7 FPGAs

ID 817758
Date 11/04/2024
Public
Document Table of Contents

5.2.2. Memory AXI4 Driver APIs

APIs to describe a traffic program for Memory AXI4 Driver.

Detailed Description

A traffic program lists commands to execute serially. The available commands are:
  • 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.