https://devzone.nordicsemi.com/f/nordic-q-a/7928/pwm-always-busyHello, I am currently working on a project where I need to be able to control an RGB by writing the PWM duty cycle to a custom BLE Service and Characteristic. I am using SDK 8.1 and s110 SoftDevice 8.0. I am also using the app_pwm library from theen-USTelligent Community 13Wed, 27 Jan 2016 03:20:02 GMThttps://devzone.nordicsemi.com/thread/28336?ContentTypeID=1Wed, 27 Jan 2016 03:20:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:80a05f0e-d23f-450b-b0ea-84d5af717f88Andrew Ong<p>Another solution is to increase the interrupt priority in app_pwm.c from APP_IRQ_PRIORITY_LOW to APP_IRQ_PRIORITY_HIGH.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/28335?ContentTypeID=1Wed, 01 Jul 2015 19:01:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:56f57b5e-b069-42e1-b84c-cecc05efd069Cory Mast<p>Thank you RK for your help. I was running them in an interrupt context. I was able to solve my problem by using the scheduler and have my LED functions execute in main context.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/28334?ContentTypeID=1Wed, 01 Jul 2015 00:38:35 GMT137ad170-7792-4731-bb38-c0d22fbe4515:55116f0c-c474-4250-9538-0ae698b873b0RK<p>What context are you in when you&#39;re doing this? Are you in an interrupt context which has higher interrupt priority than whatever the PWM module uses? If so then your spin loop never lets the module actually get the interrupt it needs to count the two ticks required to know it&#39;s set the new duty cycle and mark itself not busy so it just sits there melting the CPU spinning forever.</p><div style="clear:both;"></div>