SD 6.0.0 to SD 6.1.1 migration problem

RE: SD 6.0.0 to SD 6.1.1 migration problem

Einar Thorsrud — Mon, 26 Aug 2019 12:05:07 GMT

I see. The assert itself is because SoftDevice lost timing, so it could be caused by several things (some operation with the same or higher priority than the SoftDevice taking a too long time to finish). Other possibilities are long flash writes as was the problem in the other thread, or a timeslot that is not released in time, etc. Since you mentionned the other case - do you do long flash writes? if so, then the workaround is to split the long flash write operations in two.

RE: SD 6.0.0 to SD 6.1.1 migration problem

hossein_m — Mon, 26 Aug 2019 09:49:04 GMT

Hi Einar,

I don't think that is the case in my application, I only used Nordic standard libraries to work with interrupts which I think use critical regions. Also I don't get this assert when using soft device version 6.0.0

RE: SD 6.0.0 to SD 6.1.1 migration problem

Einar Thorsrud — Mon, 26 Aug 2019 07:43:30 GMT

Hi,

The typical reason for getting this assert is that the application disables interrupts globally instead of using critical regions (sd_nvic_critical_region_enter() / sd_nvic_critical_region_exit()). Is that the case in your code?