Hi Justin, It is an option flag that can be used with log_output module which is a helper module for formatting log messages. Most of backends does not use it. It can be easily added to certain backen

#debugging

We figured out the issue. There are some other config dependencies that I was unaware of but fiddling in menuconfig helped make it clear. These also need set (along with CONFIG_CPLUSPLUS obviously). C

#debugging

I have tried to set a break point at where the zephyr start to halt at the fatal error function, and I'm able to trace where exactly the exception happened. It ends up to the ns16550 driver in my boar

#debugging

Hi Erik, FYI, pyocd is Zephyr-aware and Nordic’s J-Link OBs can be reflashed with pyocd-compatible firmware: https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF52-DK/Download#infotabs A

#debugging #gdb #nrf52480 #ztest #bluetoothmesh

And I forgot to include the FreeRTOS part: #define configCPU_CLOCK_HZ ( SystemCoreClock ) #define configTICK_RATE_HZ ( 1000 ) Where SystemCoreClock is set to 16000000 by default.

#debugging

All I did was to uncheck the "start pyOCD locally"

#debugging #eclipse #gdb

Does the application work without the debugger attached? (i.e., did it get programmed into flash correctly?) I’ve seen weird behavior if you leave the GDB client executable at the default. Try changin

#nrf52832 #jlink #debugging #eclipse