cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
gianLuilui8
Observer
Observer
307 Views
Registered: ‎10-14-2020

XXV Ethernet (4) cores share a single parameter in xparameters.h

Jump to solution

Hello,

I am working on a project with a XXV Ethernet Subsystem. I have instantiated 4 cores in the subsystem as part of my larger design. Each core has a separate AXI4_LITE bus interfacing to the PS. The addresses have enough range to cover the register space of each individual core. 

However, when I finish generating a bitstream and export the project to Vitis, I notice that all four cores share the same CONFIG.C_BASEADDR value. I would like for them all to be separated but I don't see how to do so. Any suggestions on how to separate the 4 cores? (Address map shown below):

xxv_ethernet_4core_address_map.png

To reiterate, I would like each core to have it's own base address, statistics registers, etc. How can I do this?

The following snippet is from the auto-generated xparameters from the xsa:

/******************************************************************/

/* Definitions for driver XXVETHERNET */
#define XPAR_XXXVETHERNET_NUM_INSTANCES 1
/* Definitions for peripheral XXV_ETHERNET_0 */
#define XPAR_XXV_ETHERNET_0_DEVICE_ID 0
#define XPAR_XXV_ETHERNET_0_BASEADDR 0xA0100000
#define XPAR_XXV_ETHERNET_0_HIGHADDR 0xA010FFFF
#define XPAR_XXV_ETHERNET_0_STATS 0
#define XPAR_XXV_ETHERNET_0_PHYADDR 0

/* Canonical definitions for peripheral XXV_ETHERNET_0 */
#define XPAR_XXVETHERNET_0_DEVICE_ID 0
#define XPAR_XXVETHERNET_0_BASEADDR 0xA0100000
#define XPAR_XXVETHERNET_0_HIGHADDR 0xA010FFFF
#define XPAR_XXVETHERNET_0_STATS 0
#define XPAR_XXVETHERNET_0_PHYADDR 0
#define XPAR_XXVETHERNET_0_INTR 0xFF

 

0 Kudos
1 Solution

Accepted Solutions
longley
Xilinx Employee
Xilinx Employee
242 Views
Registered: ‎04-15-2011

The current xxvethernet driver TCL doesn't support num_cores. So it cannot generate the correct xparameters. But it will be supported in future release.

Workaround is to manually add the missing cores to the xparameters.h file

Thanks,

Longley


------------------------------------------------------------------------------------------------

Don’t forget to reply, kudo, and accept as solution.

If starting with Versal take a look at our Versal Design Process Hub and our
Versal Blogs

------------------------------------------------------------------------------------------------

View solution in original post

1 Reply
longley
Xilinx Employee
Xilinx Employee
243 Views
Registered: ‎04-15-2011

The current xxvethernet driver TCL doesn't support num_cores. So it cannot generate the correct xparameters. But it will be supported in future release.

Workaround is to manually add the missing cores to the xparameters.h file

Thanks,

Longley


------------------------------------------------------------------------------------------------

Don’t forget to reply, kudo, and accept as solution.

If starting with Versal take a look at our Versal Design Process Hub and our
Versal Blogs

------------------------------------------------------------------------------------------------

View solution in original post