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: 
Visitor syang
Visitor
1,367 Views
Registered: ‎04-11-2018

Custom MIG driver?

Jump to solution

What are the proper steps to ensure the driver has been updated correctly for the custom IP?

 

I went to the .mdd file and added the name of my custom IP to "supported_peripherals". It seem to be picking up the driver on SDK, but it does not seem to be exporting all the hardware configurations over, and I'm not able to choose the DDR3 memory on the memory map.

0 Kudos
1 Solution

Accepted Solutions
Xilinx Employee
Xilinx Employee
1,837 Views
Registered: ‎07-30-2007

Re: Custom MIG driver?

Jump to solution

Hi- there are additional TCL files in the driver that are used to automate the creation of the memory ranges. You'll have to make sure your custom core exposes the same parameters.

 

Overall, I'd suggest just defining the memory ranges yourself in the linker file.

9 Replies
Moderator
Moderator
1,333 Views
Registered: ‎02-11-2014

Re: Custom MIG driver?

Jump to solution

Hello @syang,

 

Is is this in relation to you AXI MIG migration question from a few days ago? I don’t quite understand what you are trying to do. Could you please elaborate?

 

Thanks,

Cory

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Visitor syang
Visitor
1,331 Views
Registered: ‎04-11-2018

Re: Custom MIG driver?

Jump to solution

We certified a version of the MIG back in EDK, now we are providing certification for its compatibility in Vivado.

0 Kudos
Moderator
Moderator
1,314 Views
Registered: ‎02-11-2014

Re: Custom MIG driver?

Jump to solution

Hello @syang,

 

Please follow the steps outlined in your previous thread:

 

https://forums.xilinx.com/t5/Memory-Interfaces/Migrating-EDK-MIG-to-Vivado/m-p/847750#M11831

 

AND/OR

 

UG911 for AXI MIG Migration: https://www.xilinx.com/support/documentation/sw_manuals/xilinx2018_1/ug911-vivado-migration.pdf#page=82

 

Thanks,
Cory

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Visitor syang
Visitor
1,312 Views
Registered: ‎04-11-2018

Re: Custom MIG driver?

Jump to solution

Again, these are completely irrelevant.

0 Kudos
Xilinx Employee
Xilinx Employee
1,298 Views
Registered: ‎10-19-2015

Re: Custom MIG driver?

Jump to solution

Hi @syang

After building the hardware FPGA design in Vivado, did you use the Export Hardware function? That should create a BSP that you can import to SDK. 

Thanks,

M

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
Visitor syang
Visitor
1,290 Views
Registered: ‎04-11-2018

Re: Custom MIG driver?

Jump to solution

Yea, I did. The base addresses was exported as part of the .hdf file. When I went create the memory test, the addresses does not get copied over, and I feel like the SDK is still not fully recognizing my custom IP.

0 Kudos
Visitor syang
Visitor
1,287 Views
Registered: ‎04-11-2018

Re: Custom MIG driver?

Jump to solution

@mcertosi by the way, this may help clearing thing up. My custom IP has a different name. That's why I had to add it to the .mdd file. This was all I had to do back in EDK, and it worked.

0 Kudos
Xilinx Employee
Xilinx Employee
1,838 Views
Registered: ‎07-30-2007

Re: Custom MIG driver?

Jump to solution

Hi- there are additional TCL files in the driver that are used to automate the creation of the memory ranges. You'll have to make sure your custom core exposes the same parameters.

 

Overall, I'd suggest just defining the memory ranges yourself in the linker file.

Visitor syang
Visitor
1,229 Views
Registered: ‎04-11-2018

Re: Custom MIG driver?

Jump to solution

That makes sense. My custom core still has different parameters. Thanks!