Xilinx / Xilinx/Vitis_Accel_Examples

hw_emu hangs

Open
#91 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
605
Forks
233
Avg merge
1m
Merged PRs (30d)
1

Description

No matter what example I choose, sw_emu (make run TARGET=sw_emu PLATFORM=$AWS_PLATFORM all passes successfully but hw_emu (make run TARGET=hw_emu PLATFORM=$AWS_PLATFORM all) hangs and never finishes.

The output of the command:

/bin/sh: 12: [[: not found
/bin/sh: 15: [[: not found
/bin/sh: 18: [[: not found
cp -rf ./_x.hw_emu.xilinx_aws-vu9p-f1_shell-v04261818_201920_3/emconfig.json .
XCL_EMULATION_MODE=hw_emu ./hello_world ./build_dir.hw_emu.xilinx_aws-vu9p-f1_shell-v04261818_201920_3/vadd.xclbin
XRT build version: 2.13.466
Build hash: f5505e402c2ca1ffe45eb6d3a9399b23a0dc8776
Build date: 2022-04-14 17:43:11
Git branch: 2022.1
PID: 197694
UID: 1000
[Fri Dec 31 12:00:00 2021 GMT]
HOST: 
EXE: /home/kacper/aws-fpga/Vitis/examples/xilinx_2021.2/hello_world/hello_world
[XRT] WARNING: The xrt.ini flag "opencl_summary" is deprecated and will be removed in a future release.  A summary file is generated when when any profiling is enabled, so please use the appropriate settings from "opencl_trace=true", "device_counter=true", and "device_trace=true."
[XRT] WARNING: The xrt.ini flag "opencl_device_counter" is deprecated and will be removed in a future release.  Please use the equivalent flag "device_counter."
Found Platform
Platform Name: Xilinx
INFO: Reading ./build_dir.hw_emu.xilinx_aws-vu9p-f1_shell-v04261818_201920_3/vadd.xclbin
Loading: './build_dir.hw_emu.xilinx_aws-vu9p-f1_shell-v04261818_201920_3/vadd.xclbin'
Trying to program device[0]: xilinx_aws-vu9p-f1_shell-v04261818_201920_3
INFO: [HW-EMU 07-0] Please refer the path "/home/kacper/aws-fpga/Vitis/examples/xilinx_2021.2/hello_world/.run/197694/hw_em/device0/binary_0/behav_waveform/xsim/simulate.log" for more detailed simulation infos, errors and warnings.

last 10 lines of the /home/kacper/aws-fpga/Vitis/examples/xilinx_2021.2/hello_world/.run/197694/hw_em/device0/binary_0/behav_waveform/xsim/simulate.log file:

ga/Vitis/examples/xilinx_2021.2/hello_world/.run/197694/hw_em/device0/binary_0/behav_waveform/xsim/simulate.log
INFO: [Wavedata 42-564]   Found protocol instance at /emu_wrapper/emu_i/dynamic_region//slr2/to_delete_kernel_ctrl_2/S_AXI
INFO: [Wavedata 42-564]   Found protocol instance at /emu_wrapper/emu_i/dynamic_region//user_slr_icn/M00_AXI
INFO: [Wavedata 42-564]   Found protocol instance at /emu_wrapper/emu_i/dynamic_region//user_slr_icn/M01_AXI
INFO: [Wavedata 42-564]   Found protocol instance at /emu_wrapper/emu_i/dynamic_region//user_slr_icn/M02_AXI
INFO: [Wavedata 42-564]   Found protocol instance at /emu_wrapper/emu_i/dynamic_region//user_slr_icn/S00_AXI
INFO: [Wavedata 42-564]   Found protocol instance at /emu_wrapper/emu_i/dynamic_region//user_slr_icn/m00_couplers/M_AXI
INFO: [Common 17-14] Message 'Wavedata 42-564' appears 100 times and further instances of the messages will be disabled. Use the Tcl command set_msg_config to change the current settings.
INFO: [Wavedata 42-565] Reading protoinst file protoinst_files/emu.protoinst
INFO: [Wavedata 42-565] Reading protoinst file ./dr_behav.protoinst
Time resolution is 1 ps

Any ideas why? I tried searching everywhere and couldn't find any solution. I would really appreciate any help here!

I'm using Vitis 2021.2 package.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported make run TARGET=hw_emu PLATFORM=$AWS_PLATFORM all command and compare it with the successful sw_emu run. Inspect .run/197694/hw_em/device0/binary_0/behav_waveform/xsim/simulate.log, including the point where it reaches Time resolution is 1 ps; done means hw_emu completes instead of hanging.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, shell
Domain
build-system, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.