How to change duty cycle when using HW driver library

RE: How to change duty cycle when using HW driver library

haakonsh — Tue, 10 Nov 2020 10:37:56 GMT

From nrfx_pwm.h line 142: NRFX_PWM_FLAG_LOOP

When the requested playback is finished, it will be started from the beginning. This flag is ignored if used together with @ref NRFX_PWM_FLAG_STOP. @note The playback restart is done via a shortcut configured in the PWM peripheral. This shortcut triggers the proper starting task when the final value of the previous playback is read from RAM and applied to the pulse generator counter. When this mechanism is used together with the @ref NRF_PWM_STEP_TRIGGERED mode, the playback restart will occur right after switching to the final value (this final value will be played only once).

[quote user="arikramon"]According to nrfx_pwm.h, the function nrfx_pwm_sequence_update is updating the pointer to the duty cycle values in the specified sequence during playback.[/quote]

Acoording to the documentation you should only need to call this one function in order to update the sequence values when NRFX_PWM_FLAG_LOOP is set.

RE: How to change duty cycle when using HW driver library

arikramon — Mon, 09 Nov 2020 15:06:06 GMT

If I am using flag=NRF_DRV_PWM_FLAG_LOOP, when the TASKS_SEQSTART is triggered?

is it triggered only once after nrfx_pwm_simple_playback is called?

According to nrfx_pwm.h, the function nrfx_pwm_sequence_update is updating the pointer to the duty cycle values in the specified sequence during playback.

Arik

RE: How to change duty cycle when using HW driver library

haakonsh — Mon, 09 Nov 2020 14:07:20 GMT

[quote user="arikramon"]

If I am using simple playback with two pins, with flag=NRF_DRV_PWM_FLAG_LOOP, when is the duty cycle is updated?
There is a function call "nrfx_pwm_sequence_values_update" is it safe to use it at any time?

[/quote]

If you use nrfx_pwm_sequence_values_update it will update the next time a TASKS_SEQSTART is triggered. By default, the driver triggers TASKS_SEQSTART when you call nrfx_pwm_simple_playback. You can call nrfx_pwm_simple_playback after the current loop is done or after you've called nrfx_pwm_stop.

RE: How to change duty cycle when using HW driver library

arikramon — Mon, 09 Nov 2020 11:08:10 GMT

Thank's for the answer

Two more questions:

If I am using simple playback with two pins, with flag=NRF_DRV_PWM_FLAG_LOOP, when is the duty cycle is updated?
There is a function call "nrfx_pwm_sequence_values_update" is it safe to use it at any time?

Thanks

Arik

RE: How to change duty cycle when using HW driver library

haakonsh — Mon, 09 Nov 2020 10:44:18 GMT

[quote user=""]Can I change a duty cycle in m_demo1_seq_values not in the handler routine? the Duty cycle change occurs no so often, and I don't want to enter the handler every time that NRF_DRV_PWM_EVT_FINISHED occur, as it "disturbs" the cpu[/quote]

Yes, there are two ways you can do it:

You can wait until a EVENTS_SEQSTARTED[0] event has occured. This event signals that the PWM module has read the pointer address from SEQ[0].PTR and stored it in an internal register. This is the address to your array of pwm duty-cycle samples (sequence).
At this point in time it is safe to update the SEQ[0].PTR with the address to your new sequence of duty-cycles, but it must be done before the next loop will start.
You can modify the value of your sequence directly, though this is not safe unless you can guarantee there won't be a race condition between you writing and the EasyDMA reading to/from the same address of memory at the same time. You can ensure this by either stopping the PWM, or use longer sequences and time your writing to the EVENTS_SEQSTARTED[0] event, or any other suitable event.

[quote user=""]When changing the duty cycle, when the change actually take place?[/quote]

It depends on which method you used:

When using multiple sequences, the PWM value is updated once the previous sequence is finished playing. If you are using loops, then all the loops must finish, unless you stop the PWM instance with a TASKS_STOP and then re-start it with a TASKS_SEQSTART[0].
It will change as soon as the PWM module reads an updated sequence value.