Zynq Ultrascale+ EMIO Trace Frequency - Bug in Zynq Ultrascale IP v3.3?
I'm trying to setup a cpu trace connection via EMIO with Vivado2019.1 (Zynq Ultrascale+ IP v3.3)
I have configured the MPSCO IP-Core accordingly (trace enabled via EMIO, 32bits, DBG_TRACE frequency = 250MHz). I have also created an output clock with 250MHz and connected that to the "pl_ps_trace_clk" pin.
During implementation Vivado throws pulse_width violations for the PS8/PLPSTRACECLK pin. (Required 4ns, Actual 2ns).
Why is that? I would expect a 2ns requirement since DBG_TRACE allows for up to 250MHz.
I've tested an identical setup with Vivado2018.3 (Zynq Ultrascale+ IP v3.2) and the implementation completed without violations. PS8/PLPSTRACECLK pulse width requirements were 2ns (what makes sense to me) and the cpu trace worked fine in the real world.
Could a Xilinx employee please comment on that topic.