SD 6.0.0 to SD 6.1.1 migration problem

[hossein_m]

Hello all,

I recently migrated from SDK 15.0.0 to SDK 15.3.0 and as a result tried to migrate from SD 6.0.0 to 6.1.1.

My application goes to sleep after a while and when it wakes up it should auto connect to to its host again.

The problem here is that using SD v-6.1.1 after 7 or 8 disconnect and connects the soft device asserts without any additional log info about the reason. the PC is at 0x00014AA6 when SD asserts which is in soft device.

The application works fine using SD v-6.0.0

I saw this and I wonder if I have the same problem?

Either way is there any way to resolve this issue or I have to use the soft device v 6.0.0???

thanks,

Hossein

[Einar Thorsrud]

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?

[hossein_m]

 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

[Einar Thorsrud]

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.