- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Team,
I configured iopll IP for three output clocks, (outclk0)100MHz, (outclk1)200MHz and (outclk2)600MHz. Ref clock is 100MHz.
I see duty cycle variation in the generated clock of 200MHz from iopll. I'm capturing the clocks using signal tap analyzer at a frequncy of 600MHz, genrated by same iopll.
Why the duty cycle is varying from 50%?
Clock waveform
IOPLL Settings
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You're not going to be able to see accurate sampling for a signal that fast. Rely on the timing analyzer to verify your clocks, not Signal Tap, or output to a pin and view on a scope. Signal Tap is for functional debug of data signals, not analyzing clocks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SignalTap uses a clock to capture the data, so it's dependent on that clock rate. For logic, you want it to be the same clock that drives the logic you're tapping, as you need to synchronously tap it. For probing a clock, I'm not sure exactly what you're hoping to see. Normally people have the clock drive a counter and then just sample that with another clock, to calculate X transitions happened in Y time.
Regards,
Richard Tan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi OP,
Dropping a note to ask if my last reply was helpful to you.
Do you need any further assistance from my side?
Regards,
Richard Tan

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page