UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
2,760 Views
Registered: ‎06-21-2017

Missing Interfaces in xparameters.h

Jump to solution

I am developing a project that has three AXI interfaces connected to an IP block.  I'm using a Zynq Z3EU and Vivado 2017.2.  While all three AXI interfaces show up in the address editor and after exporting to SDK, in the system.hdf file, only one interface is present in the xparameters.h file. address_ed.jpg

SystemHDF.jpg

 

The only one of these interfaes to show up in the xparameters.h file is this one:


/* Definitions for peripheral MB_TOP_0 */
#define XPAR_MB_TOP_0_BASEADDR 0x80030000
#define XPAR_MB_TOP_0_HIGHADDR 0x80031FFF

 

How do I get my other two interfaces into the file?

 

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
Moderator
Moderator
3,776 Views
Registered: ‎11-09-2015

Re: Missing Interfaces in xparameters.h

Jump to solution

Hi @bruce_karaffa,

 

1. If all of the interfaces are in the system.hdf file, does this mean that they really exist and I can just add them manually to the xparameters.h file?

> I am not really familiar with this type of cases. But you might be able to create a tcl file for your IP in your IP driver which should do it (look into some xilinx IP driver for help). It should be the correct way. The issue with writting manually to xparameter.h will be that the modification will be erased if you re-build the BSP

 

2a. Is a part of the problem that I have three AXI interfaces going into an IP block?

> Yes I guess this is part of the "issue". I wouldn't call this an issue, it is just that SDK could not be doing it by default because no Xilinx IP is design this way (at least I cannot find one).

 

2b. Is SDK trying to name each of them XPAR_MB_TOP_0  and only keeping the last one?

> Yes I guess this is what is happening (I don't really know if it is the last one or the first one (it could be that SDK cares only about one interface, so there is no loop))

 

3. If so, is there any way to force Vivado/SDK to name each interface differently?

Did you try to do it in the property window in vivado:

int.PNG

 

Hope that helps,

 

Regards,

 

Florent

 


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**

View solution in original post

0 Kudos
4 Replies
Moderator
Moderator
2,727 Views
Registered: ‎11-09-2015

Re: Missing Interfaces in xparameters.h

Jump to solution

Hi @bruce_karaffa,

 

If you are using 2017.2 you might want to have a look to AR#69489.

 

There is an issue in 2017.2 which is not updating the Hardware Platform when the hardware is re-exported?

 

Regards,

 

Florent


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
2,718 Views
Registered: ‎06-21-2017

Re: Missing Interfaces in xparameters.h

Jump to solution

A kudos for the link to the answer record.  I noticed that SDK didn't always update the BSP and I guess I stumbled into the work around.  After applying the patch, everything updates automatically. 

 

It still doesn't solve my problem.  Only one of the three AXI interfaces for the IP is showing up in the xparameters.h file.  I looked through the synthesis reports and these AXI interfaces were not removed.  All three AXI interfaces are still showing up in the system.hdf file.  A couple questions:

 

  1. If all of the interfaces are in the system.hdf file, does this mean that they really exist and I can just add them manually to the xparameters.h file?
  2. Is a part of the problem that I have three AXI interfaces going into an IP block. Is SDK trying to name each of them XPAR_MB_TOP_0  and only keeping the last one?
  3. If so, is there any way to force Vivado/SDK to name each interface differently?

 

0 Kudos
Moderator
Moderator
3,777 Views
Registered: ‎11-09-2015

Re: Missing Interfaces in xparameters.h

Jump to solution

Hi @bruce_karaffa,

 

1. If all of the interfaces are in the system.hdf file, does this mean that they really exist and I can just add them manually to the xparameters.h file?

> I am not really familiar with this type of cases. But you might be able to create a tcl file for your IP in your IP driver which should do it (look into some xilinx IP driver for help). It should be the correct way. The issue with writting manually to xparameter.h will be that the modification will be erased if you re-build the BSP

 

2a. Is a part of the problem that I have three AXI interfaces going into an IP block?

> Yes I guess this is part of the "issue". I wouldn't call this an issue, it is just that SDK could not be doing it by default because no Xilinx IP is design this way (at least I cannot find one).

 

2b. Is SDK trying to name each of them XPAR_MB_TOP_0  and only keeping the last one?

> Yes I guess this is what is happening (I don't really know if it is the last one or the first one (it could be that SDK cares only about one interface, so there is no loop))

 

3. If so, is there any way to force Vivado/SDK to name each interface differently?

Did you try to do it in the property window in vivado:

int.PNG

 

Hope that helps,

 

Regards,

 

Florent

 


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**

View solution in original post

0 Kudos
2,670 Views
Registered: ‎06-21-2017

Re: Missing Interfaces in xparameters.h

Jump to solution

 

0 Kudos