K64 FlexTimer Output Compare mode CnV register update Test

cancel
Showing results for 
Search instead for 
Did you mean: 

K64 FlexTimer Output Compare mode CnV register update Test

No ratings

K64 FlexTimer Output Compare mode CnV register update Test

Test environment:

FRDM-K64F Rev.D

IAR ARM Workbench IDE V8.30.1

MCUXpresso SDK for FRDM-K64F v2.4.2(2018-08-02)

Test project is [ftm_output_compare] located with default path: ..\FRDM-K64F\boards\frdmk64f\driver_examples\ftm\output_compare

Test reason to verify the CnV register is updated on the next FTM counter change.

Three test signals:

FTM0_CH0 pin as output compare pin will generate square signal with 1.33KHz .

FTM0_CH1 pin generate 24KHz Edge-Aligned PWM signal(High-true pulses (clear Output on match)) with 50% duty cycle as FTM counter monitor.

When FTM counter change, the FTM0_CH1 will toggle to output high voltage.

Test using a delay() function to emulate modify FTM0_CH0 output compare mode and CnV value periodically.

There is a GPIO pin will toggle after each delay() function to detect/verify the CnV value actual load point.

FlexTimer module setting:

The FTM0 refer clock is 60MHz

For the FTM0_CH1 pin generate 24KHz PWM signal, the FTM0 MOD value is fixed to 0x9C3 (60MHz/24KHz = 2500).

 

Below is the overall signals:

pastedImage_1.png

Test Process Record:

During FTM0 module initialization, set the FTM0_CH0 pin output compare value to 0xA00 (more than MOD register value (0x9C3)) with below code:

Set the CnV value more than MOD register is to avoid the output compare be set during at start.

pastedImage_3.png

After that,  enable FTM0 counter and toggle GPIO pin to set a mark:

pastedImage_4.png

After delay, toggle GPIO pin and update CnV register to 0x270 (the match point is half of the PWM high voltage).

pastedImage_5.png

The actual signal is :

pastedImage_8.png

After the first CH0 output compare set match, before set CH0 pin clear on match.

It need to keep the CH0 pin with same output compare mode and set CnV back to 0xA00 (more than MOD) again with below code:

pastedImage_6.png

Then we set CH0 with clear on match mode and update CnV value to 0x752 (middle of CH1 PWM low voltage):

pastedImage_17.png

The actual signal is:

pastedImage_18.png

With the similar code, before next CH0 set on match, it need to keep the CH0 pin with same match compare mode setting and CnV change back to 0xA00 (more than MOD).

pastedImage_7.png

pastedImage_8.png

The actual signal is below:

pastedImage_20.png

Note: During the output compare signal compare mode set/clear change phase, it need to keep previous output compare mode setting, please don't using kFTM_NoOutputSignal setting at code. Otherwise, the output compare signal will exist decay:

pastedImage_9.png

Test Result:

From FTM0 register value, the FTM0_SYNCONF[SWRSTCNT] bit is clear, which means select Legacy PWM synchronization method.

The legacy PWM synchronization method will update Output Compare mode CnV register value at the next FTM counter change.

The actual signal also verify it.

Below is FTM0 all registers value:

pastedImage_3.png

For the more detailed info, please check the original thread at here.

Please check attachment about test code.

Attachments
Comments

What to change in the code so that I  can use the RGB LED on board to get the result. such that the led is on when the PWM is high and led is off when the PWM is low 

Hi,

It recommend to change the PWM duty cycle.

best regards,

Mike

Hi

None of the RGB LEDs on the FRDM-K64F are connected to pins that support this output so you would need to rewire them to do it.
Alternatively, the timer's can be used to generate DMA transfers to the ports in question to emulate it, but that is not as efficient and so is only use in emergencies.

Regards

Mark

Version history
Revision #:
1 of 1
Last update:
‎09-11-2018 08:32 PM
Updated by: