Forum Discussion

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

Node * determined to be a clock

Hello,

TQ gives me these warnings:

--- Quote Start ---

Warning: Node: current_state.r2 was determined to be a clock but was found without an associated clock assignment.

Warning: Node: current_state.idle was determined to be a clock but was found without an associated clock assignment.

--- Quote End ---

In fitter report (control signals) I see that they are Latch enable signals for whom fitter uses global clock network.

Before continuing I think i should explain my design a little bit. The troubling part is a SRAM controller - a simple state machine. In the RTL viewer the state machines logic is masked in a block, with outputs corresponding to each state - idle, r1, r2, w1, w2.

But only the r2 acts directly as enable signal to some of the latches, but not the idle signal. So I don't think they're at fault, but honestly I'm pretty lost (not to mention the naming of nodes, nets, etc :/):

When I choose to locate these signals in RTL netlist from Fitter report (control signals), it points to the state machine block, but not to any nets (unlike with other control signals).

Also, if they actually were latch enable signals, why would fitter use global clock network for them?

I'm not sure if I have provided all the necessary information, so please ask if something additional is needed (like the code itself or smth).

Thanks in advance!

17 Replies