Might be best to abandon using the CCP HPWM at the same time until I get PWM6/7 working, that way I can config the timer registers independently and know exactly what they are. I can break off and use TMR4 later if I find that CCP PWM interferes.
Might be best to abandon using the CCP HPWM at the same time until I get PWM6/7 working, that way I can config the timer registers independently and know exactly what they are. I can break off and use TMR4 later if I find that CCP PWM interferes.
There is no technical reason that prevents simultaneous pwm use of all the CCP and PWM modules with the same timer .
I just made this example with mplabx/xc8 , it works exactly as expected.
I cannot try it with pbp as my version does not support that chip
Warning I'm not a teacher
Good to know, thanks for the input!
I've probably missed something simple, but still can't see it in my code snippet.
Ok, thanks all for verifying approach. I found the issue to be that the resolution of the duty cycle in bits was 9, not 10, (it seems it varies with the PR2 value predetermined by the HPWM command), so with the MSB of the PWMxDCH set at 1 (PWM6DCH=128), the result was "always on" at the output, whereas I was anticipating a 50% duty cycle waveform.
Bookmarks