RE: PWM SEQ0 interrupt

Sigurd — Wed, 08 May 2019 08:33:31 GMT

[quote userid="72699" url="~/f/nordic-q-a/46799/pwm-seq0-interrupt/184633"]I was able to get a ramping using a complex pwm call.[/quote]

Good.

[quote userid="72699" url="~/f/nordic-q-a/46799/pwm-seq0-interrupt/184633"]but i am still curious to know the answers to my questions on why the timer and the pwm seq0 callback was not working[/quote]

I don't see any bugs in the code you posted, and I was not able to reproduce the issue. But it could be that s_initialized= false, so that app_timer_start() was never called. Another theory could be that the LFCLK was not running, if the SoftDevice is not running, the LFCLK must be requested explicitly. See the app timer tutorial chapter called "initialization".

RE: PWM SEQ0 interrupt

dmleone — Tue, 30 Apr 2019 18:40:53 GMT

I was able to get a ramping using a complex pwm call. per below. but i am still curious to know the answers to my questions on why the timer and the pwm seq0 callback was not working

uint16_t value = PWM_RAMP_TOP;
uint8_t  i;
for (i = 0; i < 10; i++){
pwm_ramp_values[i] = value;
value              -= PWM_RAMP_TOP / 10;
}

static nrf_pwm_sequence_t const ramp_seq0 =
{
.values.p_common      = pwm_ramp_values,
.length               = NRF_PWM_VALUES_LENGTH(pwm_ramp_values),
.repeats              = 200,
.end_delay            = 0
};

static nrf_pwm_sequence_t const ramp_seq1 =
{
.values.p_common      = pwm_ramp_full_on,
.length               = NRF_PWM_VALUES_LENGTH(pwm_ramp_full_on),
.repeats              = 20000,
.end_delay            = 0
};
nrf_drv_pwm_complex_playback(&m_pwm0, &ramp_seq0, &ramp_seq1, 1, NRF_DRV_PWM_FLAG_LOOP);