PWM Sequence loop

RE: PWM Sequence loop

Felipe Ribas — Fri, 28 Apr 2017 07:57:38 GMT

I didn't properly measured but I remembed that clearly the timing was shorter than it should on seq2 when it had only one element. As if it didn't actually wait for the whole time it should but just the enough time to load the value and then reset it all....

RE: PWM Sequence loop

Bash102 — Fri, 28 Apr 2017 02:20:34 GMT

Im seeing behavior that may be related. With the goal of playing a series of sequences, the product I'm working on first calls a nrf_drv_pwm_complex_playback then on the NRF_DRV_PWM_EVT_FINISHED event a nrf_drv_pwm_simple_playback is called and given a sequence with length 1. It then does this again for a different third sequence with a longer length. The result is that the sequence with length 1 is called for a very small amount of time (~75 ms). I am toggling GPIOs on NRF_DRV_PWM_EVT_FINISHED, NRF_DRV_PWM_EVT_END_SEQ0, and NRF_DRV_PWM_EVT_END_SEQ1 to indirectly debug the timing. When I change it to length 2 and reduce the repeat counts accordingly the system behaves as expected. Have you tried measuring the timing from those events?

RE: PWM Sequence loop

Ole Bauck — Tue, 06 Dec 2016 12:13:12 GMT

Sorry for the late reply.

What is the value of nrf_pwm_sequence_t.repeats? This determine how many extra times the sequence should be played (a value of '1' should give seq1->seq1->seq2->seq2->seq1->seq1...).

I get the seq1->seq1->seq1... only if I have playback_count = 0, regardless of what value repeats are. If repeats is '1' and playback_count = 1 I get seq1->seq1->seq2->seq1->seq1->seq2...

All other values give the correct behavior.