Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
163 Views

Avalon-MM Arria V Hard IP for PCI Express Intel FPGA IP: waitrequest high

We evaluate the performance of the PCIe IP with Avalon MM interface on the Arria V FPGA. We only achieve a data rate of 1400*10^9 bytes per second which is less than written in the "PCI Express High Performance Reference Design

" document in table 10 (1784 MB per second). Using signal tap we observed that the Avalon MM waitrequest signals changes to 1 after the beginbursttransfer signal pulse during every burst.1_card_2_ch_pcie_signals_edit.png

To find the reason for this worse performance we used signal tap to monitor the fifo full and empty signals of the cmd_fifo and the wrdat_fifo inside the PCIe IP. Both full signals are never 1 so the FIFO see to be ok.

As suggested on page 18 of AN-456-2.4 we looked at the TxStReady to find out whether the PCIe core does not receive enough credit but this seems not to be the case. Do you have any advice how to solve this problem? Here the parameters of the PCIe IP:

pcie_settings.png

 

 

0 Kudos
7 Replies
Highlighted
Employee
57 Views

Hi,

Really apology for the late reply, kindly let me know you are using custom board or development board.

0 Kudos
Highlighted
Beginner
57 Views

We are using custom hardware.

0 Kudos
Highlighted
Employee
57 Views

Hi ,

To understand the issue more , kindly let me know which wait request you are mentioning , for Avalon MM there are more than one waitrequest signal. so kindly let me know which specific waitquest signal you are mentioning.

If you can let me know with respect to the block diagram mentioned , that will be great.

Page no:140

https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug-01105-1_6.pdf

 

0 Kudos
Highlighted
Beginner
57 Views

Signal TxsWaitRequest_o in Figure 7–34 on page no 139

0 Kudos
Highlighted
Employee
57 Views

Hi ,

I was doing my research and found out that the behavior is expected.

May I know why you are asserting the being burst transfer for a periodically.

If you are asserting the above signal, slave will make sure the burstcout, write and byteenable  signals are stable in the bus.

 So that is why slave is asserting the signal. Once wait request is de-asserted data will start to transfer. But if you see your waveform you are asserting the being burst transfer, periodically.

0 Kudos
Highlighted
Beginner
57 Views

See the attached image for the setup. We wrote an Avalon MM master using VHDL. It is connected to an Arria V Avalon MM PCIe IP though an AVMM interconnect that is automatically generated by QSYS. The befinbursttransfer signal you mentioned above is a signal between the automatically generated interconnect and the instantiated PCIe IP. We do not have any control over that signal.

The AVMM master asserts the write signal in every clock cycle because we want to write in every clock cycle. This is however not possible because the AVMM slave (PCIe IP) asserts waitrequest whenever we start a new burst. What is the reason for this poor performance?

 

AVMMInterconnect.png

0 Kudos
Highlighted
Employee
57 Views

Hi ,

Taking conversation in to private

0 Kudos