Uvvm clock generator not working as documented


We discovered that the uvvm clock generator is not working as documented
When using methods to set a new period, the document says: “This procedure adds a set_clock_period command to the CLOCK GENERATOR VVCs executor queue, which will run as soon as all preceding commands have completed.”

So far so good.

“When the set_clock_period command is scheduled to run, the executor will change the clock period instantly.” This is not true in all cases; when the clock is started with a high period and high time (say 1ms range) the update is only applied after a clock cycle. Additionally when changing the period the high time should be adjusted too, this is not clear from the documentation.


Hei Erick,
Thank you for pointing out the flaw. We will correct this in our next release.

Best regards,