Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
13 years ago

M_alu_result[10] was determined as clock . . . Why?!?

Hi all, I got the follwoing message from Timequest: Warning (332060): Node: ad_tpdb_qsys:inst13|ad_tpdb_qsys_nios2_0:nios2_0|M_alu_result[10] was determined to be a clock but was found wit...
Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
13 years ago

--- Quote Start ---

the message is well understood.

--- Quote End ---

I don't understand why apparently a combinational or registerd signal is used as a clock. This effectively creates a new clock domain that causes at least difficulties in timing closure with the primary clock domain. Or it would be treated as unrelated clock domain using full cross domain synchronization.