Error when generating the 'GIN' xclbin for HW. #2
Description
When trying to generate the xclbin targeting at hw for borad 'xilinx_u50_gen3x16_xdma_5_202210_1', there is an error when routing.
"ERROR: [Constraints 18-1000] Routing results verification failed due to partially-conflicted nets (Up to first 10 of violated nets): level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u[8] level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u[13] level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u[10] level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u[12] level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u[14] level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u0[1] level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u0[3] level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u0[6] level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u0[10] level0_i/ulp/GIN_compute_graphs_1/inst/grp_compute_CONV_layer_fu_5109/check_message_passing_U0/grp_finalize_fu_604/global_mean_pooling_U0/grp_global_mean_pooling_Pipeline_global_mean_pooling_tail_fu_475/sdiv_17s_32ns_16_21_1_U8048/dividend_u0[9]
"
It seems that it is a problem caused by congestion, Could you kindly tell me how to solve this problem? The original log file is attached.
runme.log
vivado.log