people shouldn't be pinging you with e-mails about such a fundamental part of the PSoC design process. This stuff should we well and publically documented.
Hi - I would have "pinged" you if I had been able to 😉
I am migrating a number of PSoC 1 designs to PSoC 3, and one UM in particular is giving me a headache - this is the PWM.. On PSoC 1 it is easy to write a value to the compare register which is only loaded / updated at TC.. But I have found no easy way to do this with the PSoC 3 PWM.
I am only just starting to use PSoC 3 (I have developed extensively using PSoC 1, and am a CYPros) and can see the huge benefits inherent in the new devices, and with time I am sure these issues will fall into place - but I do find the lack of such a fundamental function on the PWM component quite a surprise - I have tried using DMA, but even with this there are glitches on the PWM output.
Is it possible to direct me to documentation I need? - Or even better, is it possible for Cypress to create a library of components which behave in the same way as the standard UM's available for PSoC 1. I have a client who cannot understand why I am having problems implementing the PWM's on this new, far more advance part - doing the whole job on PSoC 1 took me a day, I have now spent 3 simply trying to get the PWM's to behave!
My humble apologies!
Yes, I could see that there was an API to write the compare register - but this wrote the value directly.. and as I have the pwm running continuously caused glitching ..
I believed that the PSoC 1 pwm UM was different - that the compare value was updated at TC and not instantly after writing.. Going back to PSoC Designer I find that my new (PSoC 3) code behaves exactly the same when ported (with the required changes) to the PSoC 1.. It also updates instantly and glitches!
Its been 3 years since I did anything serious with the PSoC (been out of action following heart failure) and 5 years since the project I am now moving to PSoC 3 was done - I guess I need to go back and more carefully see how I managed to avoid glitching with that design -
Sorry for this distraction - but your answer did help me to look again at the problem in a strange way.. I felt quite indignant (LOL) and was going off prove that the PSoC 3 pwm component didnt do what the PSoC 1 pwm UM could! 😉