run dilation demo error on windows

[Yangxiu123321]

windows 10 vivado hls 2019.1 xfopencv 2019.1 demo : xfopencv\HLS_Use_Model\Standalone_HLS_Example

simulation、synthesis is ok,but Co-simulation is error:

`Starting C/RTL cosimulation ... D:/programFiles/vivado/Vivado/2019.1/bin/vivado_hls.bat E:/sdsoc/code/vivado/Dilation/Dilation/solution1/cosim.tcl INFO: [HLS 200-10] Running 'D:/programFiles/vivado/Vivado/2019.1/bin/unwrapped/win64.o/vivado_hls.exe' INFO: [HLS 200-10] For user 'Yang' on host 'doom' (Windows NT_amd64 version 6.2) on Sat Jul 20 21:41:17 +0800 2019 INFO: [HLS 200-10] In directory 'E:/sdsoc/code/vivado/Dilation' Sourcing Tcl script 'E:/sdsoc/code/vivado/Dilation/Dilation/solution1/cosim.tcl' INFO: [HLS 200-10] Opening project 'E:/sdsoc/code/vivado/Dilation/Dilation'. INFO: [HLS 200-10] Opening solution 'E:/sdsoc/code/vivado/Dilation/Dilation/solution1'. INFO: [SYN 201-201] Setting up clock 'default' with a period of 10ns. INFO: [HLS 200-10] Setting target device to 'xc7z010i-clg400-1L' INFO: [COSIM 212-47] Using XSIM for RTL simulation. INFO: [COSIM 212-14] Instrumenting C test bench ... Build using "D:/programFiles/vivado/Vivado/2019.1/msys64/mingw64/bin/g++" Compiling xf_dilation_accel.cpp_pre.cpp.tb.cpp cosim.tv.mk:65: recipe for target 'obj/xf_dilation_accel.cpp_pre.cpp.tb.o' failed In file included from D:/programFiles/vivado/Vivado/2019.1/include/etc/ap_private.h:119:0, from D:/programFiles/vivado/Vivado/2019.1/include/ap_common.h:641, from D:/programFiles/vivado/Vivado/2019.1/include/ap_int.h:54, from E:/sdsoc/xfopencv/HLS_Use_Model/Standalone_HLS_Example/xf_dilation_config.h:35, from E:/sdsoc/xfopencv/HLS_Use_Model/Standalone_HLS_Example/xf_dilation_accel.cpp:31: D:/programFiles/vivado/Vivado/2019.1/msys64/mingw64/include/c++/6.2.0/iomanip:462:65: error: 'quoted' function uses 'auto' type specifier without trailing return type _CharT delim = _CharT('"'), _CharT escape = _CharT('\')) ^ D:/programFiles/vivado/Vivado/2019.1/msys64/mingw64/include/c++/6.2.0/iomanip:462:65: note: deduced return type only available with -std=c++14 or -std=gnu++14 D:/programFiles/vivado/Vivado/2019.1/msys64/mingw64/include/c++/6.2.0/iomanip:471:65: error: 'quoted' function uses 'auto' type specifier without trailing return type _CharT delim = _CharT('"'), _CharT escape = _CharT('\')) ^ D:/programFiles/vivado/Vivado/2019.1/msys64/mingw64/include/c++/6.2.0/iomanip:471:65: note: deduced return type only available with -std=c++14 or -std=gnu++14 D:/programFiles/vivado/Vivado/2019.1/msys64/mingw64/include/c++/6.2.0/iomanip:481:65: error: 'quoted' function uses 'auto' type specifier without trailing return type _CharT delim = _CharT('"'), _CharT escape = _CharT('\')) ^ D:/programFiles/vivado/Vivado/2019.1/msys64/mingw64/include/c++/6.2.0/iomanip:481:65: note: deduced return type only available with -std=c++14 or -std=gnu++14 make: *** [obj/xf_dilation_accel.cpp_pre.cpp.tb.o] Error 1 ERROR: [COSIM 212-317] C++ compile error.

ERROR: [COSIM 212-321] EXE file generate failed.

ERROR: [COSIM 212-321] EXE file generate failed.

ERROR: [COSIM 212-331] Aborting co-simulation: C simulation failed, compilation errors.

ERROR: [COSIM 212-5] *** C/RTL co-simulation file generation failed.

ERROR: [COSIM 212-4] * C/RTL co-simulation finished: FAIL *** command 'ap_source' returned error code while executing "source E:/sdsoc/code/vivado/Dilation/Dilation/solution1/cosim.tcl" invoked from within "hls::main E:/sdsoc/code/vivado/Dilation/Dilation/solution1/cosim.tcl" ("uplevel" body line 1) invoked from within "uplevel 1 hls::main {*}$args" (procedure "hls_proc" line 5) invoked from within "hls_proc $argv" Finished C/RTL cosimulation.`

[Yangxiu123321]

re.cpp.tb.cpp

-std=c++14 is ok,but I don't know why

[bgouthamb]

@Yangxiu123321

Are you following UG1233 doscument's chapter 4?

Make sure you have set the flag -DSDSVHLS for both the source and testbench files.

[nelsoncsc]

Hi @bgouthamb, I am also facing the same issue using Vivado 2018.3. Even afterr setting the flag -DSDSVHLS the C/RTL co-simulation fails. I am using Ubuntu 18.04. However, using Vivado 2018.3 in Windows cosimulation is succesful. Could you please let me know any workaround for that? Thank you

[tharaka27]

I am also facing the same issue using Vivado 2018.3. However, using Vivado 2018.3 in Windows co simulation is successful. Could you please let me know any workaround for that? Thank you