-
Notifications
You must be signed in to change notification settings - Fork 46
cuckoo_cam is a dcp built on xcvu9p-flga2104-2L-e #3
Comments
CuckooCAM is a Content Addressable Memory based on the cuckoo hashing and other few improvements. It is used to convert an incoming three tuples to a unique ID. Maybe Figure 1 here gives a better understanding. |
Oh, xcvu37p-fsvh2892-2-e Maybe because it is just a synthesized netlist? |
The current dcp should implement in any VirtexUltrascale+ except on VirtexUltrascale+ HBM. The plan is to release the code, but there are some improvements to be done and more experiments. |
Thanks Mario |
Hi @luyong6, Where are you connecting the FPGA to test link? |
@luyong6 the bring up sequence change slightly. But, I am using the same code with Vivado 2020.1 and it is working. The fact that you can link up writing the registers from the host means that something is not working properly in the interconnection between the cmac_synq and cmac. Maybe you can generate the example design for the CMAC with AXI4-Lite and check the code. |
Hi, Thx |
Hi, We are not planning to release the code in the short-term. Kintex 7 or Kintex US(+), if the latter it should work. If the former, you should check ETH implementation, they have support for series 7. https://github.com/fpgasystems/fpga-network-stack At this point I will be difficult to provide the dcp. I will try though. Mario |
Hello. I can't add the cuckoo_cam.dcp into the project vcu118_fns_single_toe_iperf. The error message is: '../cuckooCam/cuckoo_cam.dcp' is not a valid design checkpoint. Could you upload the correct file again? |
does the cuckoo_cam.dcp file exist? what it is its size? |
What is cuckoo_cam?
It is a checkpoint built on xcvu9p-flga2104-2L-e now. Is it possible to build it to other cards?
If it can also be generated by tcl or source RTLs that makes things more easier.
Thanks.
The text was updated successfully, but these errors were encountered: