Visible to Intel only — GUID: fvm1711414800145
Ixiasoft
Visible to Intel only — GUID: fvm1711414800145
Ixiasoft
6.4.2. Configuration Intercept Response Interface
The application must return the response for the request received on the Configuration Intercept Request interface using the Configuration Intercept Response interface. The GTS AXI Streaming IP will be always ready to accept responses from the application. The application will provide response data with a valid qualifier.
This interface is applicable only when operating as Endpoint mode.
Signal Name | Direction | Endpoint (EP)/Root Port (RP)/TLP Bypass (BP) | Clock Domain | Description |
---|---|---|---|---|
p0_app_ss_st_ciiresp_tvalid | Input | EP | coreclkout_hip | The application asserts this signal for one clock to indicate that valid data is driven on the p0_app_ss_st_ciiresp_tdata bus. |
p0_app_ss_st_ciiresp_tdata[32:0] | Input | EP | coreclkout_hip | Bit [31:0]: Overrides data from the application for the intercepted configuration request on the Configuration Intercept Request interface.
|
The figure below shows timing diagram for back-to-back read and write requests.
The first request sends configuration read on the Configuration Intercept Request interface for all four bytes of register located at address=0x8.
The application decides not to intercept this configuration read and hence returns tvalid=1 together with tdata[32]=0 on the Configuration Intercept Respond interface.
After receiving the first response on the Configuration Intercept Respond interface, the second request sends configuration write for byte0, byte1, and byte2 of register located at address=0x4 with data value of 0xABC. The application decides to intercept this configuration write and hence return tvalid=1 together with tdata[32]=1 on the Configuration Intercept Respond interface. Additionally, the application provides the data (i.e., 0xDEF) to be used for the intercepted configuration write on the Configuration Intercept Respond interface through tdata[31:0].