--- Quote Start ---
Info: Non-global destination nodes limited to 10 nodes
Seems as though this approach may not work as its limited to the number of nodes. I connected the clock (by wire) to another clock input pin (sclk_p2) and used it to clock the output I/O registers. I tried setting it to non-global signal, but the delay incurred was worse than for the global clock. So not sure if this approach will ever result in a saving...
--- Quote End ---
The second part of what I quoted sounds like you think the mix of global and nonglobal routing won't solve the timing problem, but my suggestion for controlling the routing probably did make it nonglobal for as many destinations as you intended.
I suspected the "limited to 10 nodes" was just a reporting limit. I verified that with my test case and in on-line help.
I changed my test case to 12 output pins (replicated the entire little circuit from input pin to output pin to create 12 copies). I got the "limited to 10 nodes" message. I got 12 nonglobal destinations for the I/O cell registers (13 in the table where the input to the global buffer is also counted) and 24 global destinations for the internal registers. You need to check your Fitter report tables like the ones I showed before to see how many destinations were made nonglobal.
The on-line help for the "limited to 10 nodes" message (right click messages to get to their help):
--- Quote Start ---
Non-global destination nodes limited to <number> nodes
--------------------------------------------------------------------------------
CAUSE: The Fitter reported the nodes which may not have been promoted to be global or use global or regional clock networks in the design.
the fitter is limiting the number of reported nodes to the specified amount. Refer to the message(s) that precede this message in the Messages window or in the Messages section of the Report Window for more information.
ACTION: No action is required.
--- Quote End ---
Honored Contributor
