NRF52840 dongle freertos Log function crash

RE: NRF52840 dongle freertos Log function crash

Vidar Berg — Wed, 26 Jul 2023 09:27:50 GMT

I recommend you downgrade your Segger to an older version that is compatible with the SDK. v5.42a is the safest option, as that was the version used at the time of the SDK release.

RE: NRF52840 dongle freertos Log function crash

Sherman Lee — Wed, 26 Jul 2023 02:07:15 GMT

My Segger studio is release 7.30 Build 2023061400.53555
Using nRF5_SDK_17.1.0

I hv connected my dongle with nrf52832 DK for jlink
But nothing appear on the debug terminal after flashing.
Maybe Im new to SES Studio, Could u share the proper way to activate it?

Thanks!

RE: NRF52840 dongle freertos Log function crash

Vidar Berg — Tue, 25 Jul 2023 09:45:04 GMT

Hi,

You can download the schematics from the product page at https://www.nordicsemi.com/Products/Development-hardware/nRF52840-Dongle/Download?lang=en#infotabs. However, the SWO is not used for RTT logging.

What version of Segger embedded studio are you using? Please note that the SDK was tested and verified with version 5.42a as stated in the SDK release notes. Version 6.20 introduced some breaking changes which affected RTT logging.

RE: NRF52840 dongle freertos Log function crash

Sherman Lee — Tue, 25 Jul 2023 01:39:38 GMT

I hv tried but nothing appear on the debug terminal.

And I see there is a SWO pin needed to connect to the Jlink but I cant really find this.

Could u share the hardware config for me?

Thanks!

RE: NRF52840 dongle freertos Log function crash

Vidar Berg — Fri, 21 Jul 2023 09:27:11 GMT

I see. I thought you were programming the dongle through DFU. Having a debugger attached makes it much easier. I suggest you try the RTT backend instead of UART without deferred logging by applying the following configurations to your sdk_config.h file:

NRF_LOG_BACKEND_UART_ENABLED  0
NRF_LOG_BACKEND_RTT_ENABLED  1
NRF_LOG_DEFERRED 0

The debug messages will be displayed in the debug terminal in Segger embedded studio when you are debugging the application.

RE: NRF52840 dongle freertos Log function crash

Sherman Lee — Fri, 21 Jul 2023 09:22:18 GMT

My DK somehow not working so I just a jlink with dongle to develop

I have added quite alot code into the example as Im porting a ESP32 project to it.

And I hv not much exp on nordic so I wanna see if anyone know the possible problems or debug direction for me. As the debug log not work as expected made my debugging process a lot harder.

Thanks!

RE: NRF52840 dongle freertos Log function crash

Vidar Berg — Fri, 21 Jul 2023 09:18:06 GMT

Sorry, I forgot you were using FreeRTOS. I tried to reproduce the problem here, but it worked for me after I applied the patch provided by Stian in the post you linked to. Do you have nRF52840 DK to try this on? The nRF52840 Dongle is not really intended for code development, it does not come with an on-board J-link debugger.

RE: NRF52840 dongle freertos Log function crash

Sherman Lee — Fri, 21 Jul 2023 08:49:44 GMT

In the example I see its use NRF_LOG_FLUSH() in the logger task.
Thats mean I need to replace FLUSH with PROCESS, and enable the log defer?
Thanks!

RE: NRF52840 dongle freertos Log function crash

Vidar Berg — Fri, 21 Jul 2023 08:40:27 GMT

Hello,

The UART logger backend will return NRF_BUSY_ERROR if there is already an ongoing UART transfer, which can happen if the log messages are processed from multiple places at the same time. Therefore, it is recommended to use LOG_DEFERRED and process the logs from the main loop with NRF_LOG_PROCESS() as we do in our BLE examples.

Best regards,

Vidar

RE: NRF52840 dongle freertos Log function crash

Sherman Lee — Fri, 21 Jul 2023 01:48:59 GMT

Also seem the debug log will affect my BLE stack.

Once I enable the log, BLE will disable around 90~100s
If I disable the backend_uart log, the BLE work fine