coexistence of softdevice + tiny OS for the application

RE: coexistence of softdevice + tiny OS for the application

Pertti Kasanen — Mon, 15 Jun 2015 17:47:00 GMT

I tried to use this and ported the latest FreeRTOS version for the nRF51 SDK 8. I'm not sure it the sd_nvic_critical_region_enter() etc. is exactly as it should be but it seems to work well for me.

The results and the experiences can be seen in devzone.nordicsemi.com/.../

RE: coexistence of softdevice + tiny OS for the application

Richard von Lehe — Wed, 22 Jan 2014 16:25:03 GMT

Thanks for the clarification on the return code. That allows one function to be used in all circumstances: softdevice enabled or disabled.

RE: coexistence of softdevice + tiny OS for the application

Ole Morten — Wed, 22 Jan 2014 12:24:56 GMT

As I said in the FreeRTOS question, using an RTOS with a softdevice isn't something we have done a lot of work on, but based on some quick experiments we do believe that it would be possible.

The general recommendation would then be to use critical_region_enter()/_exit() instead of disabling all interrupts. These functions will disable all application level interrupts, and will hence protect any application level structures against data changes. If the softdevice is not enabled, this function will return a special error code, and if so, you know that it's safe to use the regular CPSIE/CPSID instructions.