VCU reference clock requirement

[jg_bds]

PG252 indicates that the reference clock for the VCU should come from an external source:

However, when I run Block Automation on a VCU that I've added, it creates (by default) a reference clock from a PS-generated clock:

It does this instead of creating an external port for the reference clock, as it does for the MIG's reference clock.

I also see that the VCU TRD (which I don't have) is intended to run on the ZCU106 board--but I can't find a suitable external clock reference on that board which the VCU might use. 

So I'm getting mixed signals here, and I'm uncertain of the clock requirement for the VCU's Reference Clock. 

-Joe G.

[sebo]

Hello @jg_bds,

This is indeed strange.

What I can tell you, is  that VCU TRD is using an external input clock (SYS_CLK):

set_property PACKAGE_PIN AH12 [get_ports SYSCLK_300_P]
set_property PACKAGE_PIN AJ12 [get_ports SYSCLK_300_N]

On the board, it is connected to a Si570 PLL. 300 MHz is it's default value.

That clock is running at 300Mhz and feed an internal PLL with 3 output clock.

The clk_out3 is the reference clock for the VCU and set to 33.333 MHZ.

Regards,

Sébastien.

[samk · Accepted solution]

Hi @jg_bds,

As @sebo@ mentioned, theTRD can be used as a guide.

In general, the product guide takes precedence. In this case, take a look at the most recent PG252 released June 6th.

Regards,

Sam

[jg_bds]

@sebo, @samk:

Thank you for the replies. I'm now planning on tapping-off an external, 300-MHz, DDR reference clock and feeding it to the VCU after a divide-by-6 trip through a BUFGCE_DIV.

[sebo]

@jg_bds,

I'd try to run a simple implementation on the ZCU106 first in order to validate your idea.

-Sébastien.