Sign in

Search motoroladsp

Subscribe to motoroladsp

motoroladsp by Keywords

56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

Discussion Groups

Discussion Groups | Freescale DSPs | 56803 PWM duty cycle sweep speed

Technical discussions about Freescale (Motorola) DSPs (including the DSP56000, DSP56300, DSP56600, 56800 DSPs).

Post a new Thread

56803 PWM duty cycle sweep speed - Corey, Rick - Jun 14 20:11:00 2004

Hi We are presently trying to use the DSP56F803 PWM (channel 4) as a simple independent PWM output. We are sweeping the output duty cycle from 0% to 100% and therefore, updating and reloading the PWM timer on every timeout interrupt of the PWM. When we then observe the PWM output on a scope, the rate at which the PWM duty cycle is changing, is taking much longer then we would expect (4 to 5 sec to go from 0 to 100 % duty cycle). We have also seen that the rate at which this output duty cycle can be changed is somehow tied to the configured base frequency of the PWM. Is this normal operation as per the 56803 implementation of the PWM functionality? Has anyone gotten the duty cycle to change faster? The prescaler and modulus are set for PWM freq = 4.32khz. We expected the duty cycle to change in microseconds or milliseconds, not seconds. Thanks Mike Kertesz

(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

56803 PWM duty cycle sweep speed - Corey, Rick - Jun 14 20:14:00 2004

(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

56803 PWM duty cycle sweep speed - Corey, Rick - Jun 14 20:18:00 2004

Hello We are presently trying to use the DSP56F803 PWM (channel 4) as a simple independent PWM output. We are sweeping the output duty cycle from 0% to 100% and therefore, updating and reloading the PWM timer on every timeout interrupt of the PWM. When we then observe the PWM output on a scope, the rate at which the PWM duty cycle is changing, is taking much longer then we would expect (4 to 5 sec to go from 0 to 100 % duty cycle). We have also seen that the rate at which this output duty cycle can be changed is somehow tied to the configured base frequency of the PWM. Is this normal operation as per the 56803 implementation of the PWM functionality? Has anyone gotten the duty cycle to change faster? The prescaler and modulus are set for PWM freq = 4.32khz. We expected the duty cycle to change in microseconds or milliseconds, not seconds. Thanks Mike Kertesz

(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

Re: 56803 PWM duty cycle sweep speed - Douglas Holub - Jun 14 21:33:00 2004

The PWM duty cycle can only be changed at PWM period intervals. You can write to the value registers any time, but they only take effect at the beginning of the next PWM period. So at 4.32 kHz, the PWM duty cycle can only be changed every 231 usecs. If you have 16-bits of resolution, and you change the duty cycle one count at a time, it will take (231 usecs * 65535) = 15.17 seconds to sweep from 0 to 65535. If you have 15-bits of resolution, it will take 7.59 seconds, etc.

Doug Holub

----- Original Message -----

From: Corey, Rick

To: 'm...@yahoogroups.com'

Sent: Monday, June 14, 2004 3:18 PM

Subject: [motoroladsp] 56803 PWM duty cycle sweep speed

Hello We are presently trying to use the DSP56F803 PWM (channel 4) as a simple independent PWM output. We are sweeping the output duty cycle from 0% to 100% and therefore, updating and reloading the PWM timer on every timeout interrupt of the PWM. When we then observe the PWM output on a scope, the rate at which the PWM duty cycle is changing, is taking much longer then we would expect (4 to 5 sec to go from 0 to 100 % duty cycle). We have also seen that the rate at which this output duty cycle can be changed is somehow tied to the configured base frequency of the PWM. Is this normal operation as per the 56803 implementation of the PWM functionality? Has anyone gotten the duty cycle to change faster? The prescaler and modulus are set for PWM freq = 4.32khz. We expected the duty cycle to change in microseconds or milliseconds, not seconds. Thanks Mike Kertesz M...@dpconline.com

_____________________________________ /groups.php3

(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

reg:block convolution - Christ - Jun 15 6:28:00 2004

HI,

whether anyone has worked with block convolution ? can u tell the link in which the algorithm is given in detail?.i am implementing an optimum compiler for convolution.

&n bsp; thanks

&n bsp; chris

Create like a god,Command like a king,Work like a slave

------------------------------------------------------------------------------- --------------------------

R.Christober
Infineon technologies Pvt.Ltd
10th Floor,Discoverer Building
International Tech Park
Bangalore 560066.

Tel: +91 80-51392055

------------------------------------------------------------------------------- --------------------------

Yahoo! India Matrimony: Find your partner online.

(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )