Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

Dtink_cp — Sat, 06 Jul 2019 08:50:44 GMT

You can try to add two function before you configure:

app_pwm_disable(&PWM1);

err_code = app_pwm_uninit(&PWM1);

Of course, you maybe change PWM1 to which is suited with you

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

stephbur — Wed, 29 Nov 2017 12:49:30 GMT

I copied all the relevant code into the main function and disabled all imports. Now it seems to work. I will enable imports one by one and see which one was the culprit.

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

stephbur — Wed, 29 Nov 2017 12:31:09 GMT

I am using CLion for editing and gnu-make together with arm-none-eabi-gcc to compile and nrfjprog to flash. All is running on Ubuntu 17.10.

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

Sigurd — Wed, 29 Nov 2017 12:28:38 GMT

What IDE/toolchain are you using here ?

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

stephbur — Wed, 29 Nov 2017 12:26:15 GMT

#include "variables.h" #include "DAC.h" #include "DDC.h" #include "boards.h" #include "sdk_config.h" #include "setup.h" #include "nrf_gpio.h" #include "nrf_log.h" #include "nrf_delay.h"

int main(void){
    setup();
    DDC m;
    m.test_pwm();
    return 0;
}

DDC is a class which (in the future) controls a current measurement chip (this is what I need the periodic signal for). At the moment everything in that class is commented out except for some LED control which helps me debug:

void DDC::set_success(int err){
    if (err == NRF_SUCCESS){
        nrf_gpio_pin_write(18, HIGH);
        nrf_delay_ms(500);
    } else {
        nrf_gpio_pin_write(19, HIGH);
        nrf_delay_ms(500);
      }
  }

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

Sigurd — Wed, 29 Nov 2017 12:15:12 GMT

app_pwm_init takes care of initializing GPIOs, so you dont need to use the nrf_gpio_cfg_output.

nRF51 only have 3 TIMERS. nRF52832 have TIMER3 and TIMER4, but the nRF51 dont have them.

Could you upload your main.c here ?

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

stephbur — Wed, 29 Nov 2017 12:02:24 GMT

I do not use any Timer nor a SoftDevice. It happens with TIMER0, TIMER1 and TIMER2. For some reason I cannot enable TIMER3/4 to test with them. I only call app_pwm_init() once. Defining the pin with nrf_gpio_cfg_output(17); should be alright, isn't it?

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

stephbur — Wed, 29 Nov 2017 11:59:46 GMT

the only thing I call in my main function is a setup function (which defines pins as input/output) and the function written above.

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

Sigurd — Wed, 29 Nov 2017 11:53:01 GMT

Could you post the code for the main() function ?

RE: Pulsewidth modulation with app_pwm results in NRF_ERROR_INVALID_STATE

Sigurd — Wed, 29 Nov 2017 11:51:55 GMT

Hi,

The function app_pwm_init() will return NRF_ERROR_INVALID_STATE if the timer/PWM is already in use or if initialization failed. Are you calling the function app_pwm_init() more than once?