You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using openXC7 (place and route step) we get an error in BUFR module, 'u_csi_rx_top.u_phy_clk.u_bufr' to be specific.
The message we received is: ERROR: Unable to place cell 'u_csi_rx_top.u_phy_clk.u_bufr', no Bels remaining of type 'BUFR' 2 warnings, 1 error make: *** [Makefile:53: top.fasm] Error 255
This error arises from attempting to resolve this issue. We have now replaced BUFMR with BUFR, and the design was successfully tested in Vivado. @hansfbaier, @MikeReznikov Are there any indications on how we can put an end to this problem?
The text was updated successfully, but these errors were encountered:
Even if BUFMR and BUFR are internally the same component, they externally have different features, different look-and-feel, and are also treated separately in the corresponding vendor documentation.
We therefore want to track them as two separate, distinct issues.
@kerimbavcic The primitives-fixes branch has the BUFR support by @AdamLee7 already integrated.
But we need to test this branch more before merging, especially the LUTRAM changes there.
@kerimbavcic The primitives-fixes branch has the BUFR support by @AdamLee7 already integrated, if I am not mistaken.
But we need to test this branch more before merging, especially the LUTRAM changes there.
When using openXC7 (place and route step) we get an error in BUFR module, 'u_csi_rx_top.u_phy_clk.u_bufr' to be specific.
The message we received is:
ERROR: Unable to place cell 'u_csi_rx_top.u_phy_clk.u_bufr', no Bels remaining of type 'BUFR' 2 warnings, 1 error make: *** [Makefile:53: top.fasm] Error 255
This error arises from attempting to resolve this issue. We have now replaced BUFMR with BUFR, and the design was successfully tested in Vivado. @hansfbaier, @MikeReznikov Are there any indications on how we can put an end to this problem?
The text was updated successfully, but these errors were encountered: