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: 
Observer tobis
Observer
454 Views
Registered: ‎02-23-2018

Assigned Address of IP core not propagated to xparameters.h

Jump to solution

Hey guys,

I have a custom ip with an correctly assigned AXI Slave address in the address editor (0x80010000). After exporting the hardware to xsdk the address is also corretly showing up in the system.hdf file. But the xparameters.h file is showing the wrong address 0x00000000. 

(info: In my custom IP is another IP core which uses this AXI Slave interface)

 

Vivado/ XSK version: 2017.4

 

What can i do to solve this issue?

Thank you

0 Kudos
1 Solution

Accepted Solutions
Xilinx Employee
Xilinx Employee
358 Views
Registered: ‎02-01-2008

Re: Assigned Address of IP core not propagated to xparameters.h

Jump to solution

The driver used by the BSP is responsible for populating the core's address in xparameters.

If you have a custom driver for the IP, make sure the driver's tcl contains something like:

proc generate {drv_handle} {
    xdefine_include_file $drv_handle "xparameters.h" "my_regmap" "NUM_INSTANCES" "DEVICE_ID"  "C_S00_AXI_BASEADDR" "C_S00_AXI_HIGHADDR"
}

If you are not using a custom driver, make sure that the BSP driver for your IP core is set to 'generic' instead of 'none'. The generic driver will populate addresses in xparameters

0 Kudos
2 Replies
Observer tobis
Observer
400 Views
Registered: ‎02-23-2018

Re: Assigned Address of IP core not propagated to xparameters.h

Jump to solution

No one has a solution? Please help.

0 Kudos
Xilinx Employee
Xilinx Employee
359 Views
Registered: ‎02-01-2008

Re: Assigned Address of IP core not propagated to xparameters.h

Jump to solution

The driver used by the BSP is responsible for populating the core's address in xparameters.

If you have a custom driver for the IP, make sure the driver's tcl contains something like:

proc generate {drv_handle} {
    xdefine_include_file $drv_handle "xparameters.h" "my_regmap" "NUM_INSTANCES" "DEVICE_ID"  "C_S00_AXI_BASEADDR" "C_S00_AXI_HIGHADDR"
}

If you are not using a custom driver, make sure that the BSP driver for your IP core is set to 'generic' instead of 'none'. The generic driver will populate addresses in xparameters

0 Kudos