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

Okay, then you are saying that it could be that I'm not fine with my clock definition but that i also do have to examine clock domain issues?

I still believe that this must be some kind of "missunderstanding" by TQ or QSYS, because, as I said, FMax can be around 480MHz. To me it sounds as if this "clock" can cause no real problem because it seems that nothing really is connected to it. Otherwise I suppose, FMax would be much smaller . . .

Maik