cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
darin_i
Participant
Participant
1,208 Views
Registered: ‎02-15-2018

Block automation fails in Vivado 2018.2

Jump to solution

I'm following the instructions given in PG195 (04-04-2018) for generating the IPI example design and it fails with the following cryptic message:

 

apply_bd_automation -rule xilinx.com:bd_rule:xdma -config { accel {1} auto_level {Subsystem Level} axi_clk {Maximum Data Width} axi_intf {AXI Memory Mapped} bar_size {Disable} bypass_size {Disable} c2h {2} cache_size {32k} h2c {2} lane_width {X1} link_speed {5.0 GT/s (PCIe Gen 2)}}  [get_bd_cells xdma_0]
missing operator at _@_
in expression "...ne eq "X8") && ($link _@_$LS_5_GTS "
ERROR: [#UNDEF] Error found in procedure apply_rule.
 missing operator at _@_
in expression "...ne eq "X8") && ($link _@_$LS_5_GTS "

 

report_ip_status claims everything is up-to-date.

 

Anyone come across this before?

 

Thanks

 

 

0 Kudos
1 Solution

Accepted Solutions
darin_i
Participant
Participant
1,091 Views
Registered: ‎02-15-2018

Hi Cory,

 

It is not a Xilinx board, if that's what you're asking. It's a carrier board sold by a third party. I will work around the issue (if I continue using this board to be honest). The board manufacturer has stated they will repair their board files to be compatible with IPI.

View solution in original post

4 Replies
darin_i
Participant
Participant
1,183 Views
Registered: ‎02-15-2018

Replying to my own post :-)

I read back through the example in PG195 and thought "let me  try an older rev of Vivado"

I tried the same thing in 2017.4... same result.

0 Kudos
darin_i
Participant
Participant
1,145 Views
Registered: ‎02-15-2018

Solved it.

Problems in the board definition data hosed the block automation process.

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

Hello @darin_i,

 

Are you using a custom board file or a provided board file i.e. KCU105, etc. Also what did you change the resolve the issue?

 

Thanks,

Cory

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
darin_i
Participant
Participant
1,092 Views
Registered: ‎02-15-2018

Hi Cory,

 

It is not a Xilinx board, if that's what you're asking. It's a carrier board sold by a third party. I will work around the issue (if I continue using this board to be honest). The board manufacturer has stated they will repair their board files to be compatible with IPI.

View solution in original post