Loopback Delay Estimation Design on PlutoSDR

1. The idea behind mentioning Pluto in the other post is to indicate that the design is simple enough that it could fit in Pluto's Zynq Z-7010. But, the original design was tested for ADI RF SOM only. Once the design has been optimized to fit on a Zynq Z-7010, Pluto Support package alone should be enough.

2. Line 151 is only specifying the name of the folder into which the build artifacts get saved when you run hdlworkflow.m script.

- Srikanth

1. The idea behind mentioning Pluto in the other post is to indicate that the design is simple enough that it could fit in Pluto's Zynq Z-7010. But, the original design was tested for ADI RF SOM only. Once the design has been optimized to fit on a Zynq Z-7010, Pluto Support package alone should be enough.

2. Line 151 is only specifying the name of the folder into which the build artifacts get saved when you run hdlworkflow.m script.

- Srikanth

Thank you for the answer.

I also have access to a ZedBoard with a FMCOMMS4-EBZ would it run on that without optimization?

Best,
Ottega

The design uses valids to implement counters and other control mechanisms that trigger the computations performed. These valids might need to be updated to point to those in FMCOMMS4 design. The algorithm itself will likely not need any update.  

You are likely to be DSP limited by this design. You will need ~102 DSP48s without modifying the design. A Zedboard can accommodate that.

-Travis