cancel
Showing results for 
Search instead for 
Did you mean: 
381 Views
Registered: ‎11-19-2019

SDK BSP: Custom IP Version in Driver

Jump to solution

[Vivado 2017.2.1 on Ubuntu 14.04.6]

I’m writing a XSCT Tcl script which builds an application project, similar to this flow:

https://www.xilinx.com/html_docs/xilinx2018_1/SDK_Doc/xsct/use_cases/xsct_howtoruntclscriptfiles.html

So in short:

setws, repo -set, createhw, createbsp, createapp

 

For repo -set, I’m following the structure recommended here:

https://www.xilinx.com/support/answers/35443.html

 

The result is this set of errors:

1.png

createhw then runs successfully.

createbsp throws a similar error but it’s fatal:

2.png

They seem to be HSI-related errors pertaining to the driver definitions of one custom IP. We implement other custom IP in the build (all sourced from .xci), but the one throwing this error was created with SysGen (not sure if it matters).

 

Where could this version issue originate from? How can I resolve it?

 

Additional References:

https://forums.xilinx.com/t5/Embedded-Development-Tools/Custom-IP-driver-defining-include-files/td-p/781655

(tried this)

 

https://forums.xilinx.com/t5/Processor-System-Design/How-to-add-driver-to-custom-IP/td-p/667643

( I don’t fully understand the HSI Tcl commands shown here, but I’m cross referencing it with:

)

1.png
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Moderator
Moderator
263 Views
Registered: ‎09-12-2007

Re: SDK BSP: Custom IP Version in Driver

Jump to solution

mdd.PNG

The issue is the version format:

OPTION version = 1.60.16;

 

Can you change this to:

OPTION version = 1.0;

 

For example, see the GPIO:

https://github.com/Xilinx/embeddedsw/blob/master/XilinxProcessorIPLib/drivers/gpio/data/gpio.mdd

View solution in original post

0 Kudos
4 Replies
Highlighted
Moderator
Moderator
319 Views
Registered: ‎09-12-2007

Re: SDK BSP: Custom IP Version in Driver

Jump to solution

Looks like the tools are struggling with your MDD file. The MDD file is used to link the IP detected in the HDF/XSA with the drivers in the repo directories using the supported_peripherals parameter. For example, here is the axi_gpio:

https://github.com/Xilinx/embeddedsw/blob/master/XilinxProcessorIPLib/drivers/gpio/data/gpio.mdd

Can you share your MDD file? Is it in the correct folder? Also, this is a unix file, so if you created this in win, then it might be worth running a dos2unix on it (dos2unix custom_driver.mdd)

0 Kudos
Highlighted
312 Views
Registered: ‎11-19-2019

Re: SDK BSP: Custom IP Version in Driver

Jump to solution

Hi, thank you for your suggestions. To your points:

(1) MDD file attached*. OPTION version matches the actual version of the current IP.

(2) The path shown in the error messages matches the actual location of the MDD file in question.

(3) The "golden project" originated in Windows, you're correct that the MDD was in DOS format. I tried dos2unix; unfortunately my script returns the same set of errors.

 

*actual MDD extension resulted in upload errors

0 Kudos
Highlighted
Moderator
Moderator
264 Views
Registered: ‎09-12-2007

Re: SDK BSP: Custom IP Version in Driver

Jump to solution

mdd.PNG

The issue is the version format:

OPTION version = 1.60.16;

 

Can you change this to:

OPTION version = 1.0;

 

For example, see the GPIO:

https://github.com/Xilinx/embeddedsw/blob/master/XilinxProcessorIPLib/drivers/gpio/data/gpio.mdd

View solution in original post

0 Kudos
Highlighted
206 Views
Registered: ‎11-19-2019

Re: SDK BSP: Custom IP Version in Driver

Jump to solution

Hi, thanks for the reply. I changed this line in the MDD file which I have in my repo location.

So,  repo -set  will run correctly with this manual fix.

Since I'm scripting the flow,  createbsp  still struggles. It references the MDD file which was extracted from my Vivado HDF when  createhw  was executed, not the repo MDD.

I can do a  file copy -force  of my repo MDD to overwrite that extracted MDD, but this seems like a poor solution.

Instead, can I change how the MDD is generated for the custom IP? Or tell  createbsp  to reference the repo drivers instead? Any documentation references or pointers are appreciated (still new to SDK). Thanks!

0 Kudos