Hello, There is a difference that the PWM is a bean with hardware-independ interface that doesn't need a PWMMC device so it also doesn't support special features of the PWMMC device on the Freescale MCUs like fault protection or complementary PWM pairs. Please see the PWMMC help for details. If you don't plan to port the application to an MCU without PWMMC peripheral, I recommend to use the PWMMC bean to let the generated code benefit from the hardware's features. best regards Petr Hradsky Processor Expert Support Team UNIS --- In motoroladsp@moto..., "Ko Ihara" <kihara@g...> wrote: > > I'm using 56F805 to control a number of DC controllers. The DSP is > hooked up to a separate H-bridge, which receives two digital signals > for direction, and one PWM for current control (for 1 motor). > > Is there an advantage to using PWMMC over the regular PWM bean? All > the functionality seems to be in PWM already, so what's the advantage > of PWMMC? >

I'm using 56F805 to control a number of DC controllers. The DSP is hooked up to a separate H-bridge, which receives two digital signals for direction, and one PWM for current control (for 1 motor). Is there an advantage to using PWMMC over the regular PWM bean? All the functionality seems to be in PWM already, so what's the advantage of PWMMC?