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
As pointed in the README for RDMA-based connections, I was referring to AlveoLink. Their default target for Hivenet and cmac packages (.xo files) is U55c card. I see in few of the examples of TAPA-CS, U250 is considered. For example: ( line9: --part-num xcu250-figd2104-2L-e) in file apps/multi-fpga-vadd/run_tapa.sh.
Should Hivenet and cmac .xo files be regenerated for U250? or can the same U55c .xo files be used for U250 as well? can you please clarify on this.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi
As pointed in the README for RDMA-based connections, I was referring to AlveoLink. Their default target for Hivenet and cmac packages (.xo files) is U55c card. I see in few of the examples of TAPA-CS, U250 is considered. For example: ( line9: --part-num xcu250-figd2104-2L-e) in file
apps/multi-fpga-vadd/run_tapa.sh
.Should Hivenet and cmac .xo files be regenerated for U250? or can the same U55c .xo files be used for U250 as well? can you please clarify on this.
Thanks.
The text was updated successfully, but these errors were encountered: