[VTA] Cannot generate VTA bitstream file

#1

Hi Expert,

I follow this https://docs.tvm.ai/vta/install.html#vta-fpga-toolchain-installation

The log seem OK as below:
"Run output will be captured here:
vta_xlconcat_1_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_xlconcat_1_0_synth_1/runme.log
vta_wgt_mem_1_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_wgt_mem_1_0_synth_1/runme.log
vta_wgt_mem_0_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_wgt_mem_0_0_synth_1/runme.log
vta_out_mem_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_out_mem_0_synth_1/runme.log
vta_store_queue_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_store_queue_0_synth_1/runme.log
vta_store_0_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_store_0_0_synth_1/runme.log
vta_processing_system7_1_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_processing_system7_1_0_synth_1/runme.log
vta_s2g_queue_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_s2g_queue_0_synth_1/runme.log
vta_gemm_queue_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_gemm_queue_0_synth_1/runme.log
vta_inp_mem_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_inp_mem_0_synth_1/runme.log
vta_g2s_queue_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_g2s_queue_0_synth_1/runme.log
vta_g2l_queue_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_g2l_queue_0_synth_1/runme.log
vta_load_queue_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_load_queue_0_synth_1/runme.log
vta_proc_sys_reset_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_proc_sys_reset_0_synth_1/runme.log
vta_l2g_queue_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_l2g_queue_0_synth_1/runme.log
vta_load_0_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_load_0_0_synth_1/runme.log
vta_axi_smc_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_axi_smc_0_synth_1/runme.log
vta_fetch_0_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_fetch_0_0_synth_1/runme.log
vta_compute_0_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_compute_0_0_synth_1/runme.log
vta_axi_timer_1_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_axi_timer_1_0_synth_1/runme.log
vta_xbar_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_xbar_0_synth_1/runme.log
vta_auto_pc_0_synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/vta_auto_pc_0_synth_1/runme.log
synth_1: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/synth_1/runme.log
[Mon Jun 17 03:11:52 2019] Launched impl_1…
Run output will be captured here: /home/tvm/tvm/vta/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/vta.runs/impl_1/runme.log
launch_runs: Time (s): cpu = 00:00:27 ; elapsed = 00:00:31 . Memory (MB): peak = 2388.207 ; gain = 453.574 ; free physical = 3122 ; free virtual = 4545

wait_on_run impl_1

[Mon Jun 17 03:11:52 2019] Waiting for impl_1 to finish…
[Mon Jun 17 03:17:56 2019] impl_1 finished
wait_on_run: Time (s): cpu = 00:00:00.71 ; elapsed = 00:06:04 . Memory (MB): peak = 2388.207 ; gain = 0.000 ; free physical = 1068 ; free virtual = 1431

if {[file exist $proj_path/$proj_name.runs/impl_1/${proj_name}_wrapper.bit]} {

file mkdir $proj_path/export

file copy -force $proj_path/$proj_name.runs/impl_1/${proj_name}_wrapper.sysdef \

$proj_path/export/vta.hdf

file copy -force $proj_path/$proj_name.runs/impl_1/${proj_name}_wrapper.bit \

$proj_path/export/vta.bit

}

exit

INFO: [Common 17-206] Exiting Vivado at Mon Jun 17 03:17:58 2019…"

but i cannot see the vta.bit file

Can anyone help me?

Thanks

#2

From the log you pasted, it seems that the bitstream was generated. It is kinda weird that you have a home folder named tvm? does this path /home/tvm/tvm/vta exists?

if so, then you can go to the tvm root folder and try find . -name "*.bit"

#3

Hi Vegaluis,

Thank for your reply.

" does this path /home/tvm/tvm/vta exists?"

yes

" if so, then you can go to the tvm root folder and try find . -name "*.bit""

i tried but not see vta.bit file

Do you have other idea?

Thanks you

#4

I would try the following:

  1. can you paste here the output of this command echo $HOME?

  2. Open this runme.log and check if there are any issues about not being able to write the bitstream file?

  1. Do you have enough space on that path? check with df -h
#5

the first, I’d like to describe our procedure (history of change) as below:

  • I set-up VMware with Ubuntu 16.04.6 LTS
  • Step 1: follow vta-fpga-toolchain-installation guide, the result (already set RAM size greater than 4G in VMware) is vivado crashed
    "/home/tvm/Xilinx/Vivado/2018.2/bin/loader: line 194: 21144 Killed “$RDI_PROG” “$@”
    Makefile:116: recipe for target ‘/home/tvm/tvm/vta/hardware/xilinx/…/…/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/export/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0.bit’ failed
    make: *** [/home/tvm/tvm/vta/hardware/xilinx/…/…/build/hardware/xilinx/vivado/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0/export/1x16x16_8bx8b_15_15_18_17_142MHz_6ns_v0_0_0.bit] Error 137
    "
  • Step 2: after googled, i add this command: unset GNOME_DESKTOP_SESSION_ID before make vta bitstream, the result same as first post in this thread (the log seem OK but don’t see vta.bit file)

The second, follow your suggestion:
" can you paste here the output of this command echo $HOME ?"

/home/tvm

“Open this runme.log and check if there are any issues about not being able to write the bitstream file?”

i not found any runme.log file

" 3. Do you have enough space on that path? check with df -h"

The terminal output as below:
“tvm@ubuntu:~/tvm/vta/hardware/xilinx$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.2G 0 3.2G 0% /dev
tmpfs 645M 9.3M 635M 2% /run
/dev/sda1 39G 33G 3.6G 91% /
tmpfs 3.2G 288K 3.2G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.2G 0 3.2G 0% /sys/fs/cgroup
tmpfs 645M 56K 645M 1% /run/user/1000”

Thank you

#6

Oh I see, that is why you have a tvm home directory, you have a setup a virtualmachine with that user.

Have you tested “Vivado” alone to see if this is an issue with the installation? Can you try to generate a bitstream from a simple project to test this?

You are also close to run out of space look see /dev/sda1 39G 33G 3.6G 91% /

#7

" You are also close to run out of space look see /dev/sda1 39G 33G 3.6G 91% /"

after i extend the partition, i can get vta.bit file (no need hack around with unset GNOME_DESKTOP_SESSION_ID)

thank you for your help

#8

Hi vegaluis，

sorry to bother you, but l meet the same question. l have searched and tried many ways but still can’t succeed.

i can successful tested ‘vivado’ and my space is used 65% , do you have more idea about this question?

thanks a lot!

image