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

Hi,

QSYS does create an SDC file which I also included in my TQ analysis.

However, there are no clocks defined in this SDC file. Maybe that is the problem. It seems that I solved th issue by applying my own clock definition to this signal. It#s just a little unconfotable that I have to care about QSYS timing constraints, as I don't really know what the mentioned signal is doing.

Thanks for you hints regarding the correct usage of report_timing!

Maik