Closed lloo099 closed 2 years ago
hi @maltanar , could u help me with this? thanks
Hi @lloo099 , can you describe the steps you are following to get this error?
If you are running report_ip_status
outside Docker, the errors about not finding the weight streamer IP can be a false alarm because the path for that IP is normally specified to be inside the Docker container (/workspace/finn/finn-rtllib/memstream
). When opening the same project outside of Docker for synthesis or debugging, you'll need to add the host-side path (something like /path/to/finn/finn-rtllib/memstream
) to the list of IP repos.
Hi @lloo099 , can you describe the steps you are following to get this error?
If you are running
report_ip_status
outside Docker, the errors about not finding the weight streamer IP can be a false alarm because the path for that IP is normally specified to be inside the Docker container (/workspace/finn/finn-rtllib/memstream
). When opening the same project outside of Docker for synthesis or debugging, you'll need to add the host-side path (something like/path/to/finn/finn-rtllib/memstream
) to the list of IP repos.
Hi, I following this
export VIVADO_PATH=/tools/Xilinx/Vivado/2020.1
export FE_PATH=/home/enai/Desktop/project/finn-examples-main/finn_examples
export PYNQ_IP=192.168.1.7
export VITIS_PATH=/tools/Xilinx/Vitis
source /opt/xilinx/xrt/setup.sh
export PLATFORM_REPO_PATHS=/opt/xilinx/platforms
export FINN_XILINX_PATH=/tools/Xilinx
export FINN_XILINX_VERSION=2020.1
./run-docker.sh build_custom /home/enai/Desktop/project/finn/build/mobilenetv1
Hi @lloo099 , can you describe the steps you are following to get this error? If you are running
report_ip_status
outside Docker, the errors about not finding the weight streamer IP can be a false alarm because the path for that IP is normally specified to be inside the Docker container (/workspace/finn/finn-rtllib/memstream
). When opening the same project outside of Docker for synthesis or debugging, you'll need to add the host-side path (something like/path/to/finn/finn-rtllib/memstream
) to the list of IP repos.Hi, I following this
export VIVADO_PATH=/tools/Xilinx/Vivado/2020.1 export FE_PATH=/home/enai/Desktop/project/finn-examples-main/finn_examples export PYNQ_IP=192.168.1.7 export VITIS_PATH=/tools/Xilinx/Vitis source /opt/xilinx/xrt/setup.sh export PLATFORM_REPO_PATHS=/opt/xilinx/platforms export FINN_XILINX_PATH=/tools/Xilinx export FINN_XILINX_VERSION=2020.1 ./run-docker.sh build_custom /home/enai/Desktop/project/finn/build/mobilenetv1
btw, I cannot find this fold "vivado_stitch_proj_82a0t6qf". Do u know how to generate it?
Does it failed due to insufficient memory? u may check runme.log file.
[10:08:13] Starting bitstream generation..
[10:13:22] Run vpl: Step impl: Failed
[10:13:24] Run vpl: FINISHED. Run Status: impl ERROR
ERROR: [VPL 60-773] In '/tmp/finn_dev_enai/vitis_link_proj_3oie5ezy/_x/link/vivado/vpl/vivado.log', caught Tcl error: problem implementing dynamic region, impl_1: route_design ERROR, please look at the run log file '/tmp/finn_dev_enai/vitis_link_proj_3oie5ezy/_x/link/vivado/vpl/prj/prj.runs/impl_1/runme.log' for more information
WARNING: [VPL 60-732] Link warning: No monitor points found for BD automation.
ERROR: [VPL 60-704] Integration error, problem implementing dynamic region, impl_1: route_design ERROR, please look at the run log file '/tmp/finn_dev_enai/vitis_link_proj_3oie5ezy/_x/link/vivado/vpl/prj/prj.runs/impl_1/runme.log' for more information
ERROR: [VPL 60-1328] Vpl run 'vpl' failed
ERROR: [VPL 60-806] Failed to finish platform linker
INFO: [v++ 60-1442] [10:13:24] Run run_link: Step vpl: Failed
Time (s): cpu = 00:02:47 ; elapsed = 04:32:39 . Memory (MB): peak = 1336.637 ; gain = 0.000 ; free physical = 23993 ; free virtual = 24457
ERROR: [v++ 60-661] v++ link run 'run_link' failed
ERROR: [v++ 60-626] Kernel link failed to complete
ERROR: [v++ 60-703] Failed to finish linking
INFO: [v++ 60-1653] Closing dispatch client.
Looking at the runme.log you shared, it ends with:
/tools/Xilinx/Vivado/2020.1/bin/loader: line 286: 6912 Killed "$RDI_PROG" "$@"
which is probably because it's running out of memory. Vitis/Alveo builds need a lot of memory (at least 64GB, or more if you are running other things at the same time / using the NUM_DEFAULT_WORKERS
env.var. for build parallelism) https://finn.readthedocs.io/en/latest/getting_started.html#system-requirements
Hi, I following this
export VIVADO_PATH=/tools/Xilinx/Vivado/2020.1 export FE_PATH=/home/enai/Desktop/project/finn-examples-main/finn_examples export PYNQ_IP=192.168.1.7 export VITIS_PATH=/tools/Xilinx/Vitis source /opt/xilinx/xrt/setup.sh export PLATFORM_REPO_PATHS=/opt/xilinx/platforms export FINN_XILINX_PATH=/tools/Xilinx export FINN_XILINX_VERSION=2020.1 ./run-docker.sh build_custom /home/enai/Desktop/project/finn/build/mobilenetv1
btw, I cannot find this fold "vivado_stitch_proj_82a0t6qf". Do u know how to generate it?
vivado_stitch_proj_82a0t6qf
should be under /tmp/finn_dev_enai
-- you can also specify the FINN_HOST_BUILD_DIR
environment variable to place those generated files somewhere else before running the script.
Looking at the runme.log you shared, it ends with:
/tools/Xilinx/Vivado/2020.1/bin/loader: line 286: 6912 Killed "$RDI_PROG" "$@"
which is probably because it's running out of memory. Vitis/Alveo builds need a lot of memory (at least 64GB, or more if you are running other things at the same time / using the
NUM_DEFAULT_WORKERS
env.var. for build parallelism) https://finn.readthedocs.io/en/latest/getting_started.html#system-requirementsHi, I following this
export VIVADO_PATH=/tools/Xilinx/Vivado/2020.1 export FE_PATH=/home/enai/Desktop/project/finn-examples-main/finn_examples export PYNQ_IP=192.168.1.7 export VITIS_PATH=/tools/Xilinx/Vitis source /opt/xilinx/xrt/setup.sh export PLATFORM_REPO_PATHS=/opt/xilinx/platforms export FINN_XILINX_PATH=/tools/Xilinx export FINN_XILINX_VERSION=2020.1 ./run-docker.sh build_custom /home/enai/Desktop/project/finn/build/mobilenetv1
btw, I cannot find this fold "vivado_stitch_proj_82a0t6qf". Do u know how to generate it?
vivado_stitch_proj_82a0t6qf
should be under/tmp/finn_dev_enai
-- you can also specify theFINN_HOST_BUILD_DIR
environment variable to place those generated files somewhere else before running the script.
Hi, thanks. It seems ur right. My RAM is only 32GB. So does it have a new way to build it on 32GB? Or I must to upgrade my RAM to least 64GB.
Hi @maltanar and all, I encounter some errors about synth_1 problems. And u may see below information and report_ip_status, it seems some ip cannot be found. But I follow your steps to generate finn ips. How to deal with it? thanks,
Platform: U200 model: Mobilenetv1 Ubuntu:18.04 Vitis:2020.1