- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How good is the phase locked loop on the PSOC 4?
I'm seeing clock stop for a tiny bit every so often.
I see you have an issue here:
But, is the same IP used in the phase locked loop on PSOC 4?
I only change the divisor and the fractional divisor.
I never stop it.
It is set to start up automatically in the system-wide resources.
Is there an errata on this? An application note? Any document?
What if we reference our clock to a USB device?
A crystal?
Which is most reliable?
Need some external reference.
- Labels:
-
PSoC 4 Architecture
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
can a usb trim state cause a 1/(48,000,000/64k) second resync timeout?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What if I change the frequency using the api? Will it have a dead-time of over a ms?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So is it really required to stop the clock, just to change the frequency? Or just figure it might not run past the trigger point and run
through the entire counter (1.3 ms of dead time)? Is it best to reduce this possibility by stopping the clock, changing the freq, and then starting it?
It seems so to me.
So, it seems it IS required to stop the clock if you want a clean change of freq.
But, if you stop the clock.. [catch 22]
Anyone have a better answer?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Could you please elaborate what is [catch 22]. And what all are the issues you are facing if you stop and start the clock
Thanks
Ganesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I want no glitch