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 vandenplas
Visitor
1,059 Views
Registered: ‎11-02-2017

Revision stack

I'm compiling the revision stack for the ZCU102

 

I get the following error No M_AXI_GP port found in the platform!

0 Kudos
5 Replies
Moderator
Moderator
1,031 Views
Registered: ‎09-12-2007

Re: Revision stack

Are you using the platform for the zcu102 that is delivered with the tools?

0 Kudos
Visitor vandenplas
Visitor
1,021 Views
Registered: ‎11-02-2017

Re: Revision stack

I'm following the instructions from :

 

http://www.wiki.xilinx.com/reVISION+Getting+Started+Guide+2017.4+rev2?responseToken=9ead30c8981a368cb91bebd1f84cbccc

 

I've got both the ZCU102 and ZCU104

 

I've also tried to see if I can fix the issue by setting up my own custom platform.

 

 

 

0 Kudos
Visitor vandenplas
Visitor
1,010 Views
Registered: ‎11-02-2017

Re: Revision stack

I've tried a new build using the ZCU104 and I still get the same error

0 Kudos
Observer marie-laurie
Observer
922 Views
Registered: ‎05-16-2018

Re: Revision stack

Hi Vandenplas

 

I have the same error, did you manage to solve this issue ? 

regards, 

ML

0 Kudos
Xilinx Employee
Xilinx Employee
781 Views
Registered: ‎05-23-2016

Re: Revision stack

While this error is where the tool is halting, you very likely saw some suspicious messages related to clock ID prior to the reported error.  Things like this:

WARNING: [DMAnalysis 83-1005] Invalid clock id 1 for platform XYZ

 

Typically this is the result of a naming mismatch between the platform and the platform's content.  You can encounter this if the platform directory has been renamed, or if the .dsa file internal to the platform has been renamed or was incorrectly exported.  An example way of recreating this problem would be to download the revision platform, and renamed the containing directory [the directory containing the .xpfm file] to "revision" instead of leaving it named what it was originally [something like zcu102_rv_ss or whatever it was].  Unfortunately, names are important, and at least today renaming causes mismatches down-stream.