2024 - LatticeECP3: How do I determine the delay of a LaticeECP3 DCS cell from a Place and Route TRACE Report?
A DCS (Dynamic Clock Select) element only drives primary clock nets. That is why the DCS cell delay is not presented by itself in a Place and Route TRACE Report. A TRACE report will show a 0 delay through the DCS cell. Instead, the sum of the DCS and and primary clock network delay is lumped as a whole into the DCS output clock net delay in the TRACE report.
Below is an example from a TRACE report, where the DCS cell delay (MUX_DEL) is 0 and the total cell and route delay is lumped into the global clock (ROUTE):
Name Fanout Delay (ns) Site Resource
PADI_DEL --- 0.457 C12.PAD to C12.PADDI clk0
ROUTE 1 0.870 C12.PADDI to ULDCS0.CLK0 clk0_c
MUX_DEL --- 0.000 ULDCS0.CLK0 to ULDCS0.DCSOUT DCSInst0
ROUTE 4 0.474 ULDCS0.DCSOUT to IOL_T2A.CLK dcsout_inferred_clock
--------
1.801 (25.4% logic, 74.6% route), 2 logic levels.