FreeRTOS app and Softdevice runtime fault

RE: FreeRTOS app and Softdevice runtime fault

RTMerkel — Tue, 24 Mar 2020 22:05:27 GMT

I have a similar issue; how to get MMD and FreeRTOS working together on a nRF52833 dev board.

Looking at https://github.com/NordicPlayground/j-link-monitoring-mode-debugging/blob/master/pca10040/s132/ses/ble_app_blinky_pca10040_s132.emProject, it seems that project doesn't support FreeRTOS as there are not external/freertos references.

The issue, as I see it:

JLINK_MONITOR.c calls app_timer_pause/resume(), which are not defined in app_timer_freertos.c
j-link-monitoring-mode-debugging contains app_timer2.c which does define app_timer_pause/resume()
examples/ble_peripheral/ble_app_hrs_freertos contains app_timer_freertos.c, and not app_timer2.c.

My assumptions are

JLINK_MONITOR.c must call app_timer_pause/resume(), and
.Ffor MMD + FreeRTOS, a project must include app_timer_freertos.c and NOT app_timer2.c.

Is that correct?

If so, then it appears that app_timer_freertos.c needs app_timer_pause/resume(). I believe FreeRTOS has timer pause and resume functions so this should be a bit issue.

Thanks in advance,

Randy

RE: FreeRTOS app and Softdevice runtime fault

feran — Wed, 13 Nov 2019 16:58:23 GMT

Thank you for the help, and the MMD tip. The debugging halts seem to have been the culprit of the issue.

RE: FreeRTOS app and Softdevice runtime fault

bjorn-spockeli — Tue, 12 Nov 2019 15:19:32 GMT

Hi Feran,

[quote user=""]In both cases the SEGGER debugger breaks at address 0xA60, and finally if resuming execution, we'll end up in the app fault handler with origin address 0x24c92. This happens in both Debug and Release configurations and can be forced to occur more by pausing and resuming execution repeatedly. This forcing procedure is what I have been doing as preparation for this post. Normally I'm developing with the Debug configuration running and there the error shows up sometimes by itself.[/quote]

After enabling the SoftDevice you cannot halt and resume execution as this may cause the SoftDevice to HardFault. You can set breakpoints and halt at them, but we recommend resetting the chip instead of resuming execution.

It is possible to use Monitor Mode debugging to avoid this limitation, see https://github.com/NordicPlayground/j-link-monitoring-mode-debugging/#monitor-mode-debugging-in-keil-%C2%B5vision5-and-segger-embedded-studio

Best regards

Bjørn