Add KR260 reference design example

[vmayoral]

Connected to #146.

[alexforencich]

Please make sure this is clear of any output files (there are some under tb that should be removed). Also, if there are no button/switch inputs, there is no need for debounce_switch. Please also clean up all of the commented out code - if it's not relevant to the KR260, it should be deleted completely.

Also, I don't think the KR260 requires a Vivado license, so that language should probably be removed from the readme.

[alexforencich]

Also, if this is for the SFP+ module and the board also has 1G interfaces, please rename KR260/fpga to KR260/fpga_10g so that later on KR260/fpga_1g can be added.

[vmayoral]

Addressed comments above @alexforencich, let me know if you're missing anything.

[vmayoral]

Nit added at 2e69f50, left-over from dev changes. Consistent now with the rest of the repo.

[vmayoral]

Renamed also as requested above @alexforencich.

[russell-t]

@vmayoral I tried compiling the 10g example using Vivado 2023.1. I get errors that module 'zynq_ps' is not found resulting in synthesis failing. Opening fpga.xpr in Vivado, I see that zynq_ps_inst, gtkwizard_ultrascale_v1_7_16.eth_xcvr_gt_full_gtwizard_gthe3, gtkwizard_ultrascale_v1_7_16.eth_xcvr_gt_full_gtwizard_gtye3,
gtkwizard_ultrascale_v1_7_16.eth_xcvr_gt_full_gtwizard_gtye4, and eth_xcvr_gt_channel all have a question mark next to their names.

[vmayoral]

Hey @russell-t,

It's been a while since I looked at this last time. Note that this reference design was built with Vitis/Vivado 2022.1 (see #146). I'd encourage you to try things out with that version instead.

Cheers,

[vmayoral]

Closing this ticket to avoid idle PRs around. Feel free to re-open/rebase/merge if of interest at some point in the future.

I'll leave the submitted version at the following branch alive: https://github.com/vmayoral/verilog-ethernet/tree/kr260-pr

[alexforencich]

@russell-t you need to source all of the TCL files in the ip directory.

@vmayoral we should definitely get KR260 support merged in some form. Do you want to work on this PR a bit more, or should I just put together a set of reference designs myself for the different interfaces on the KR260?

[vmayoral]

@vmayoral we should definitely get KR260 support merged in some form. Do you want to work on this PR a bit more, or should I just put together a set of reference designs myself for the different interfaces on the KR260?

@alexforencich happy to rework it if needed, sure. Any particular fixes that you miss in here? Branch per se is operational as per my last testing and addressed your previous comments. Let me know if you're missing anything else.