No drivers are generated when Creating a new AXI peripheral

[yu_chenthu08]

Hi all,

      I'm tying the latest Vivado/Vitis 2020.1 and have found a problem when "Creating a new AXI peripheral". No driver files for the AXI interfaces were generated automatically after I created the IP. In the former 2019 version a simple template driver were generated for the basic read/write on the AXI register/memory.

      Two related phenomena are as below:

      1) The tcl command called during the "Creating a new AXI peripheral" is "generate_peripheral -example_design ... -bfm_example_design..." while in the former version "-driver" was used.

      2) The drvier files we obtained from the former version Vivado seem to cause a make failure in the latest Vitis IDE. It seems to be related with the makefile but I don‘t know why.

      Could you please help solve the problem? Thanks!

[HarisA]

I am currently facing the same problem. Did you manage to find any solution?

[HarisA]

Hi again,

I've managed to find a solution. The problem seemed to lie within the Makefile. I used one of the preexisting driver Makefiles within Vitis when creating a platform project as template, simply replacing the names within the used file with the name of my new AXI peripheral. I was then able to successfully assign the driver to my peripheral and use the driver files within an application.

[syedz · Accepted solution]

@yu_chenthu08 

This is a known issue that will be fixed in future vivado release. For 2020.1, the workaround is to create the AXI4 peripheral IP in 2019.2 and add the custom IP repository in 2020.1. 
Users can Edit the IP in 2020.1 using Edit in IP packager by right-clicking the added custom IP from IP catalog. They should now see the software driver file group in 2020.1.

--Syed