SoftDevice 6.0.0 to 6.1.X migration

RE: SoftDevice 6.0.0 to 6.1.X migration

Simonr — Wed, 05 Jun 2019 11:31:54 GMT

Hi Josh

I think you are having similar issues to this case, where the code is writing too large chunks of data to the flash at one time. This is a bug with the S140 SoftDevice, and the workaround (for now) is to split long writes into multiple shorter ones. It is explained in-depth in this case.

Best regards,

Simon

RE: SoftDevice 6.0.0 to 6.1.X migration

josh-m — Mon, 03 Jun 2019 21:27:37 GMT

We have the -DDEBUG flag set, and I flipped on NRF_SDH_BLE_LOG_ENABLED for a build and didn't see any new warnings/errors at compile or build time. We're already throwing over 50 kB at the heap, so I don't think that's the issue. If it was, I don't think things would fail so consistently.

I traced a bit further into things, and it seems like the PC passed into the error handler is always 0x14a3a (for SD 6.1.0). Hoping someone from Nordic can provide me a hint based off of what might be going on in the SD at that address.

I also noticed that things seem to be pretty consistently failing at a freeRTOS app_timer_stop() call. Not sure what to make of that, the exact same logic causes no issues when running against the 6.0.0 SD. The timer is definitely properly initialized, I tired a build with a bigger max timer queue size and timer task stack size (FreeRTOSConfig.h) and it didn't make any difference.

Thanks,

Josh

RE: SoftDevice 6.0.0 to 6.1.X migration

BinderT — Mon, 03 Jun 2019 19:09:10 GMT

Just a shot in the dark.
Have you enable the compiler debug flag (CFLAGS += -DDEBUG) with NRF_SDH_BLE_LOG_ENABLED 1 in the sdk config. This will tell you if the SD requirements need to be adjusted in the linker.
Provided the following is set correctly in the sdk config.

NRF_SDH_BLE_PERIPHERAL_LINK_COUNT
NRF_SDH_BLE_CENTRAL_LINK_COUNT
NRF_SDH_BLE_TOTAL_LINK_COUNT
NRF_SDH_BLE_GAP_EVENT_LENGTH
NRF_SDH_BLE_GATT_MAX_MTU_SIZE
NRF_SDH_BLE_GATTS_ATTR_TAB_SIZE
NRF_SDH_BLE_VS_UUID_COUNT
NRF_SDH_BLE_SERVICE_CHANGED

Good rule of thumb I found when using FreeRTOS on the NRF52s is to chuck 32K at the TOTAL_HEAP_SIZE and reduce when application is done.