Hi Andre,
Virtual pins essentially turn into registers in the current implementation, and hence require a clock for (at least most) timing constraints and the associated timing analysis. The message below is harmless. It is telling you that you didn't assign a clock to the Virtual Pin via the "Virtual Pin Clock" assignment, and that Quartus can't find a reasonable clock to use as a default clock for this Virtual Pin. Quartus searches the fan-in and fan-out cone of the Virtual Pin to see if there's a clock the Virtual Pin feeds or is fed by -- if it finds one, that becomes the default clock for this Virtual Pin. In this case it couldn't find a clock, so this Virtual Pin presumably feeds / is fed by combinational logic only. The code simply gnds the clock.
If you don't care about timing analysis of paths starting or ending on these virtual pins, you don't have to do anything.
If you do care about their timing analysis, you can use the "Virtual Pin Clock" assignment to specify what clock domain you want them to be part of. Or, you can simply specify a "Maximum Delay" timing constraint to or from these virtual pins, if that's easier and matches what you want.
Hope this helps,
Vaughn Altera [v b e t z (at) altera.com]
I have constrained some pins in my top-level design as virtual pins: (Altera QuartusII v. 4.2 SP1
To Assignment Name Value Enabled Pin_name Virtual Pin On Yes ...
After fitting I get the following warning message for all constrained output pins:
Warning : Can't fit auto-select clock for virtual pins "Pin_name1"
-- setting clock to GND Warning : Can't fit auto-select clock for virtual pins "Pin_name2"
-- setting clock to GND ...
When looking at the Quartus Help it is said under ACTION : Assign the Virtual Clock Pin logic option to an appropriate clock signal in the design.
But I have not chosen a Virtual CLOCK Pin assignment but Virtual Pins !!! So why do I get these warnings ?
Rgds André