Can we specify cut timing path along with the code?

--- Quote Start ---

Sorry for being a bit pedantic on the synch-chain.

But did the quote from the 'QII 13.0 Help' help?

--- Quote End ---

I apologize for my inobservance. Somehow I overlooked the quote in your post. Yes, the attribute solves the problem.

I mean to have searched the Quartus Software Handbook before, but ended up with the impression that the signal specification in the attribute must provide a full node name as in the respective tcl or qsf statement. But this isn't the case and to achieve there are enough examples to see how it works.

You are also right that standard metastability MTBF requires double registering before the XOR. In the specific application, one register level has been spared to achieve lower delay, because a certain failure rate (getting zero or double output pulses) can be accepted in this case. But I won't suggest it generally.

Thanks,

Frank