cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
bhwxl123
Contributor
Contributor
580 Views
Registered: ‎12-13-2019

XDMA does not work well with vivado 2020.2.2

I have a project built with the XDMA IP in vivado 2020.1 for XC7K325T-2FFG900I and it works perfectly, but when I upgrade the vivado project to 2020.2 It does not work! I only update some built-in IP versions as the GUI suggests and make no other modifications.
Here are the error logs:

bhwxl123_3-1615017824357.png

I add some code to capture irq_id and cfg_id to libxdma.c

bhwxl123_5-1615017966133.png

The project works well built by vivado 2020.1 works as below:

bhwxl123_1-1615017776824.png

Maybe I encountered the same problem as https://forums.xilinx.com/t5/PCIe-and-CPM/XDMA-IP-not-working-in-2020-2-but-OK-in-2019-2/m-p/1209163#M18145

If Xilinx made some modifications to XDMA IP that the driver does not support or it is some other problems?

 

0 Kudos
7 Replies
pvenugo
Moderator
Moderator
500 Views
Registered: ‎07-31-2012

@bhwxl123 ,

Could you please provide me more details on XDMA IP configuration? May be you XCI file will help.

Please elaborate "I only update some built-in IP versions as the GUI suggests and make no other modifications.".

Are you saying which ever IP needs update in 2020.2 you have done it as per Vivado tool?

 

Meanwhile, I'd suggest you to try XDMA IP from scratch on its example design in 2020.2 and test onboard.

 

Regards

Praveen


-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
470 Views
Registered: ‎08-19-2019

Hello

We have the same problem. 2019.2 worked well, 2020.2 does not work (updated via Vivado tool). I tried also the empty project with XDMA only and it does not work either. The XDMA cannot read its internal registers on any BAR. We have also a Windows driver which also does not read any BAR registers from XDMA 2020.2 version, so it is not related to Linux driver. The problem must be in the XDMA.

Does anybody know if the bug is related to Vivado version or XDMA version? I have Vivado v2020.2 and XDMA v4.1 rev8. It worked well with Vivado 2019.2 and XDMA v4.1 rev4. But I did not test other combinations.

Ondrej

0 Kudos
bhwxl123
Contributor
Contributor
433 Views
Registered: ‎12-13-2019

I open the project worked well built by vivado 2020.1 with vivado 2020.2.2, and take operations as the GUI suggests:

bhwxl123_0-1615346529911.png

bhwxl123_1-1615346580552.png

bhwxl123_2-1615350462680.png

Then I clicked the "Upgrade Selected" button, and then validate design, generate output products, run synthesis, run implementation, generate bitstream.

the original xci and the upgraded files are here

 

 

0 Kudos
bhwxl123
Contributor
Contributor
433 Views
Registered: ‎12-13-2019

Here are my XDMA configs

bhwxl123_3-1615351160935.png

bhwxl123_4-1615351172896.png

bhwxl123_5-1615351183549.png

bhwxl123_6-1615351207939.png

bhwxl123_7-1615351228968.png

bhwxl123_8-1615351243999.png

 

 

0 Kudos
bhwxl123
Contributor
Contributor
433 Views
Registered: ‎12-13-2019

I ran the drivers and applications on ubuntu 18.04 and encountered the problem

0 Kudos
bhwxl123
Contributor
Contributor
381 Views
Registered: ‎12-13-2019

0 Kudos
dianfengqishi
Visitor
Visitor
207 Views
Registered: ‎04-16-2020

Me too.

vivado 2020.1 works well but faild using 2020.2

The same error, xdma driver report  interruptID and configID are both ZERO.

log.jpg

0 Kudos