Design assistant - reporting violating paths

--- Quote Start ---

The design assistant has a few violating rules for clock crossings in our design. It lists the start point and endpoint, but doesn't list the path between the two.

I haven't seen any options yet to enable logging of the violating path, so you can see when the domain crossing happens. Does anyone know if it's possible to do so?

Thanks,

baver

--- Quote End ---

Hi Baver,

Critical Warning: (High) Rule D101: Data bits are not synchronized when transferred between asynchronous clock domains. Found 8 asynchronous clock domain interface structure(s) related to this rule.

Critical Warning: Node "inst[7]"

Critical Warning: Node "inst[6]"

Critical Warning: Node "inst[5]"

Critical Warning: Node "inst[4]"

Critical Warning: Node "inst[3]"

Critical Warning: Node "inst[2]"

Critical Warning: Node "inst[1]"

Critical Warning: Node "inst[0]"

select one of the critical warning, right mouse clock -> locate e.g RTL view

Kind regards

GPK

Pletz,

I have a design with two very disparate clocks (125MHz and 7.8MHz). The 7.8MHz is generated in RTL, using a counter, which is based on the 125MHz clock. We chose to implement two "send and capture" signals based on this same counter to provide known points in time to "send" new data to the 7.8MHz domain and to "capture" data back from it, relative to the 125 domain. My concern is if we false-path the actual "data" flops, there will be no constraint on their transfer to the 7.8MHz domain. As such ,we implemented multicycle constraints, yet are still seeing the D101 critical warnings and are concerned the tool is not doing what we want it to and even perhaps over compensating.

Any ideas on how to approach this?