Migration from SDK 5.2 to 6.0 and SD 6.0 to 7.0 issues

[Jeremy Hubbard]

Hi,

I am migrating to the latest code versions (both SDK and Softdevice) but I am having issues when I start the notifications on a BLE app. The errors I am seeing are almost identical to what is seen here.

After notifications are enabled it transmits data as expected for about 1 second, then it crashes in the timeout_handler_exec() subroutine when m_evt_schedule_func() returns with error 4, No Memory for operation. I have tried increasing SCHED_QUEUE_SIZE from 30 (which worked before the migration) to 100. I have tried increasing APP_TIMER_OP_QUEUE_SIZE from 15 to 40, and I have tried increasing APP_TIMER_MAX_TIMERS from 6 to 10. None of these things, or a combination has any noticeable effect on when the scheduler queue fills up and throws the error.

I did leave the old SPI driver from the previous SDK in place when I migrated, because it was lightweight and worked just fine.

Any help or insight would be greatly appreciated.

Thanks,

Jeremy

EDIT:

I have since run 2 more tests with my setup.

1. Using the old SDK (v5.2) with the new softdevice (v7), the exact same issue occurs. One characteristic gets notifications just fine, but as soon as the second characteristic transmits once it crashes inexplicably with no memory.

2. Using the new SDK (v6.0) alongside the old softdevice (v6), the device works exactly as it is supposed to.

Is there something that needs to happen for the new softdevice to transmit notifications for multiple characteristics or is there some sort of memory leak due to the new softdevice?

Thanks

[Stefan Birnir Sverrisson]

Hi Jeremy

We do not provide any guide on how to port your code between major nRF51 SDK releases. The method that is generally used to port custom application between major nRF51 SDK releases is to copy the custom code, block by block, into a similar example in the new SDK. For example, if I had made a custom application based on the ble_app_hrs example, I would copy the custom code into the ble_app_hrs example in the new SDK.

Also, SD 7.0.0 is only compatible with SDK 6.0.0 and SD 6.0.0 is only compatible with SDK 5.2.0

[Lucas]

Stefan,

Is this truly the easiest way to do it? I was going to attempt to look through the release notes and migration document, but if you feel this is the best method I will proceed that way. Can you link me to the latest version of the ble_app_hrs example. I don't know where that is located.

[Stefan Birnir Sverrisson]

My experience is that it is easier to copy custom code from SDK v5.2.0 into similar code template in version 6.0.0, than to actually try to port your code. This is mainly because the bond-manager in version 5.2.0 is replaced by the device-manager in version 6.0.0, see release notes for nRF51 SDK v6.0.0.

[Jeremy Hubbard]

After copying the custom code into the ble_app_hrs example it started working as expected.