Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some problem in implementing the accelerator for PageRank on Alveo U280 platform #1

Open
hhhhjun opened this issue Mar 15, 2023 · 1 comment

Comments

@hhhhjun
Copy link

hhhhjun commented Mar 15, 2023

Hi, I encountered the following problems when running code on U280. My system is Ubuntu 20.04.5. My vitis version is Vitis-Tutorials-2022.2. The device I used is xilinx_u280_gen3x16_xdma_1_202211_1.
And the error is reported as follows :ERROR: [Constraints 18-1000] Routing results verification failed due to partially-conflicted nets (Up to first 10 of violated nets): level0_i/ulp/littleKernelScatterGather_10/inst/Loop_readEdges_proc3_U0/grp_Loop_readEdges_proc3_Pipeline_readEdges_fu_96/din[58] level0_i/ulp/bigKernelScatterGather_1/inst/accGather_4_U0/grp_accGather_4_Pipeline_VITIS_LOOP_299_2_fu_34/one_update_tuple_update_V_reg_419[3] level0_i/ulp/bigKernelScatterGather_1/inst/accGather_4_U0/grp_accGather_4_Pipeline_VITIS_LOOP_299_2_fu_34/lshr_ln_reg_433_reg[14]_0[10] level0_i/ulp/bigKernelScatterGather_1/inst/Loop_readEdges_proc4_U0/grp_Loop_readEdges_proc4_Pipeline_readEdges_fu_108/edge_burst_stm_din[92] level0_i/ulp/bigKernelScatterGather_1/inst/Loop_readEdges_proc4_U0/grp_Loop_readEdges_proc4_Pipeline_readEdges_fu_108/edge_burst_stm_din[88] level0_i/ulp/bigKernelScatterGather_1/inst/Loop_readEdges_proc4_U0/grp_Loop_readEdges_proc4_Pipeline_readEdges_fu_108/edge_burst_stm_din[87] level0_i/ulp/bigKernelScatterGather_1/inst/Loop_readEdges_proc4_U0/grp_Loop_readEdges_proc4_Pipeline_readEdges_fu_108/edge_burst_stm_din[86] level0_i/ulp/bigKernelScatterGather_1/inst/Loop_readEdges_proc4_U0/grp_Loop_readEdges_proc4_Pipeline_readEdges_fu_108/edge_burst_stm_din[84] level0_i/ulp/bigKernelScatterGather_1/inst/Loop_readEdges_proc4_U0/grp_Loop_readEdges_proc4_Pipeline_readEdges_fu_108/edge_burst_stm_din[82] level0_i/ulp/bigKernelScatterGather_1/inst/Loop_readEdges_proc4_U0/grp_Loop_readEdges_proc4_Pipeline_readEdges_fu_108/edge_burst_stm_din[81]
I want to know how to solve this problem. Thank you.

@Matsubarai
Copy link

Matsubarai commented Jan 2, 2024

I faced the same problem recently. My solution is to add --kernel_frequency=250 option in v++ linking, and it works at 220 MHz. A modified version with Vitis 2022.2 support is here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants