If you use remote_host to distribute compile jobs across a Linux farm, 2020.2 still occasionally loses file handles over NFS. The workaround (mounting with noac ) is still required.
# This now works flawlessly in 2020.2 foreach impl_run [get_runs impl_*] current_run $impl_run place_design save_checkpoint -as $impl_run.post_place.dcp route_design save_checkpoint -as $impl_run.post_route.dcp xilinx vivado 20202 fixed
if:
The release of Vivado 2020.2 introduced significant changes to Xilinx's (now AMD's) design suite, such as the integration of the Vitis unified software platform, which replaced the traditional SDK for embedded development. While this version brought new capabilities for Versal and other advanced devices, it also came with its own set of unique bugs that required specific fixes. If you use remote_host to distribute compile jobs
exec vivado -mode batch -source $env(XILINX_VIVADO)/data/regression/regression.tcl While this version brought new capabilities for Versal
The write_checkpoint -incremental command would sometimes generate reference design files that the implementation tools could not read. This resulted in the tool falling back to a full compile, wasting 4-8 hours of engineering time.
For users of Vivado HLS (integrated into the Vivado 2020.2 environment), the transition from algorithmic C/C++ simulation to hardware implementation is streamlined through the ap_fixed library. This library allows designers to define arbitrary precision types directly in C++.
