RE: LFCLK Failsafe

Petter Myhre — Fri, 11 Nov 2016 12:53:08 GMT

If you try to change the clock source while the SoftDevice is enabled you will get a hardfault, so that is not an option. So softdevice_handler_sd_disable() doesn't return, and I'm assuming that sd_softdevice_disable() doesn't either?

You could access NVM directly, the SoftDevice doesn't stop you from doing this, but I recommend doing some testing. I'm not sure what will happen if the crystal disconnected and connected again.

Another solution may be to have the unlogged data in a section of RAM that is retain through a reset, then when you detect crystal disconnection you can set a bool and reset. On boot you check the bool if there is data that should be written to flash. Then you can even enable the SoftDevice again with the LF RC as source. I haven't tested this, it is just an idea.

RE: LFCLK Failsafe

cole — Thu, 10 Nov 2016 23:39:07 GMT

Hi Petter,

I'm using SDK version 10.0.0 and Softdevice S110 v8.0.0

Thanks, Cole

RE: LFCLK Failsafe

Petter Myhre — Wed, 09 Nov 2016 10:06:23 GMT

I'm not sure if it is possible, but I will look into it. What SoftDevice and SDK version are you using?