06-11-2019 07:38 AM
I can package my HDL code into a complete IP core and use it in my block designs. My core has an AXI lite interface and I wrote a driver (simple .c and .h sources) that I'd like to include in the SDK project (bare metal Zynq design).
These two files are added as Software Drivers in a "xilinx_softwaredriver" file group in the IP. The integrator now requires a MLD or MDD file for use with the SDK.
Are there any examples/guides on how to achieve that? Any template? Or am I wrong in the assumption that I can include my drivers in the IP core?
Thanks in advance!
06-12-2019 04:37 PM
You can create a driver/data/driver.mdd file. You can use the baremetal drivers delivered with SDK as reference, Or ug1138
The MDD has an associated TCL file of the same name (In same data folder)
The BSP uses the supported peripheral info in the MDD against the info in the HDF to link the IP with the driver. So make sure the IP NAME matches your custom HDL IP
Let me know if you have any questions?
06-15-2019 12:51 PM
Okay, I managed to write the tcl and mdd file. The hw/bsp and application projects are generated but I can't include my driver header file (No such file or directory). In the hardware project I see my header under
How do I configure the SDK to search for the header? Also the source file is not compiled automatically (located at the same location as the header). How do I add the source file to the build dependencies?
06-17-2019 06:48 AM
Unfortunately I can't share the hdf file because of confidentiality reasons. I can however ensure that the driver mdd/tcl/c and h file are contained in the hdf file. They get loaded into SDK as well (see attahced screenshot) but don't get compiled and the toolchain can't find the header pfc.h.
06-17-2019 11:34 AM
Can you right click on your bsp in project explorer view in SDK and select board support package settings
Select drivers and scroll down to your IP and make sure your driver is selected ( or might be set to generic)