Forum Discussion

HongLiang's avatar
HongLiang
Icon for New Contributor rankNew Contributor
2 years ago

Aglix F-tile P&R error

we try to put an F-tile PHY into our design

there are some error that occurs

Error (22144): Cannot place the block dp_rx|rx_phy_top_inst|u_dp_gxb_rx|directphy_f_0|dphy_hip_inst|persystem[0].perxcvr[1].fgt.rx_ux.x_bb_f_ux_rx at location fgt_q0_ch0_rx because the connected cell dp_rx|rx_phy_top_inst|u_dp_gxb_rx|directphy_f_0|dphy_hip_inst|persystem[0].perehip_rx[1].rx_ehip.x_bb_f_ehip_rx|bb_f_ehip_rx_xcvr25g0 can only be placed in location(s) bb_f_ehip_rx_xcvr25g[1], bb_f_ehip_rx_xcvr25g[5], bb_f_ehip_rx_xcvr25g[9], bb_f_ehip_rx_xcvr25g[13], bb_f_ehip_rx_xcvr25g[17], bb_f_ehip_rx_xcvr25g[21].


Error (22658): Cannot place block dp_rx|rx_phy_top_inst|u_dp_gxb_rx|directphy_f_0|dphy_hip_inst|persystem[0].perxcvr[1].fgt.rx_ux.x_bb_f_ux_rx in location fgt_q0_ch0_rx because it makes the block dp_rx|rx_phy_top_inst|u_dp_gxb_rx|directphy_f_0|dphy_hip_inst|persystem[0].perxcvr[2].fgt.rx_ux.x_bb_f_ux_rx unplaceable

Error (22658): Cannot place block dp_rx|rx_phy_top_inst|u_dp_gxb_rx|directphy_f_0|dphy_hip_inst|persystem[0].perxcvr[1].fgt.rx_ux.x_bb_f_ux_rx in location fgt_q0_ch0_rx because it makes the block dp_rx|rx_phy_top_inst|u_dp_gxb_rx|directphy_f_0|dphy_hip_inst|persystem[0].perxcvr[3].fgt.rx_ux.x_bb_f_ux_rx unplaceable

Error (22144): Cannot place the block dp_rx|rx_phy_top_inst|u_dp_gxb_rx|directphy_f_0|dphy_hip_inst|persystem[0].perxcvr[1].fgt.rx_ux.x_bb_f_ux_rx at location fgt_q0_ch1_rx because the connected cell dp_rx|rx_phy_top_inst|u_dp_gxb_rx|directphy_f_0|dphy_hip_inst|persystem[0].perehip_rx[1].rx_ehip.x_bb_f_ehip_rx|bb_f_ehip_rx_xcvr25g0 can only be placed in location(s) bb_f_ehip_rx_xcvr25g[1], bb_f_ehip_rx_xcvr25g[5], bb_f_ehip_rx_xcvr25g[9], bb_f_ehip_rx_xcvr25g[13], bb_f_ehip_rx_xcvr25g[17], bb_f_ehip_rx_xcvr25g[21].

what are the problems?

is possible for the pin allocation to conflict?

I just keep the pin assignment free run by Quartus and not specify the pin allocate.

5 Replies