rtl_kernel examples in 2018.2: "requires 4 arguments" error (gen_xo.tcl)

0

Hello

I recently updated my on-premise development tools to 2018.2, and the rtl_kernel examples are failing with error against the gen_XXX.tcl script.

For example, for the following example:
aws-fpga/SDAccel/examples/xilinx_2018.2/getting_started/rtl_kernel/rtl_vadd

when I run this make command:
make check TARGETS=hw_emu DEVICES=$AWS_PLATFORM_DYNAMIC_5_0 all

I get the following error:

mkdir -p xclbin
/extra/opt/Xilinx/Vivado/2018.2.op2258646/bin/vivado -mode batch -source scripts/gen_xo.tcl -tclargs xclbin/vadd.hw_emu..xo vadd hw_emu

****** Vivado v2018.2.op (64-bit)
**** SW Build 2258646 on Thu Jun 14 20:02:38 MDT 2018
**** IP Build 2256618 on Thu Jun 14 22:10:49 MDT 2018
** Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.

source scripts/gen_xo.tcl

if { $::argc != 4 } {

puts "ERROR: Program "$::argv0" requires 4 arguments!\n"

puts "Usage: $::argv0 <xoname> <krnl_name> <target> <device>\n"

exit

}

ERROR: Program "scripts/gen_xo.tcl" requires 4 arguments!

Usage: scripts/gen_xo.tcl <xoname> <krnl_name> <target> <device>

INFO: [Common 17-206] Exiting Vivado at Mon Apr 1 15:35:37 2019...
mkdir -p xclbin
/extra/opt/Xilinx/SDx/2018.2.op2258646/bin/xocc -l --xp "param:compiler.preserveHlsOutput=1" --xp "param:compiler.generateExtraRunData=true" -s -o xclbin/vadd.hw_emu..xclbin -t hw_emu --platform /home/tytra/aws-fpga/SDAccel/aws_platform/xilinx_aws-vu9p-f1-04261818_dynamic_5_0/xilinx_aws-vu9p-f1-04261818_dynamic_5_0.xpfm xclbin/vadd.hw_emu..xo

****** xocc v2018.2_AR71715 (64-bit)
**** SW Build 2258646 on Thu Jun 14 20:02:38 MDT 2018
** Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.

ERROR: [XOCC 60-602] Source file does not exist: /home/tytra/aws-fpga/SDAccel/examples/xilinx_2018.2/getting_started/rtl_kernel/rtl_vadd/xclbin/vadd.hw_emu..xo
ERROR: [XOCC 60-623] Unsupported input file type specified.
make: *** [xclbin/vadd.hw_emu..xclbin] Error 1

Can someone kindly advise on this? I get a similar error for any example in the rtl_kernel folder.

Many thanks,

Waqar.

asked 5 years ago181 views
1 Answer
0

Hello

I've managed to spot the issue here. There was a Python script that required Python version 2.7.x, whereas I was using Python 3.x. Moving back to 2.7.x sorts the issue.

Specifically, Python 3.X fails on this python script: $(COMMON_REPO)/utility/parsexpmf.py (used by Make).

Thanks,

Waqar.

answered 5 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions