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

I would have thought this was easy but I cannot seem to find a way to prevent LOG_INF etc from adding a line break to the log string. I have found the following log flag definition in log_output.h #de

#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

Hi All, We're trying to turn on debug optimizations, with C++ support. We have the following settings in our prj.conf: CONFIG_DEBUG_OPTIMIZATIONS=y CONFIG_NO_OPTIMIZATIONS=y but this leads to an undef

#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 All, I'm trying to enable Zephyr with a SoC(4-cores CPU) that not listed in the Zephyr page. Currently I'm able to step the code using the ARM Development studio and able to step (single step) unti

#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

Hi, We are looking for direction on how best to improve our (multi-threaded) debugging capability. Current setup: host ---NRF52_dev_board (onboard jLink) -- custom Nordic-SoC board where host is macOS

#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

Hi there, Thanks for the feedback and sorry for the delay. Here is my function that initializes the clock, it is called right after HAL_Init(): // Configure the main internal regulator output voltage

#debugging

Hi David, I'm not a SWO user myself but I'm suspecting a clock set up issue. On FreeRTOS, what was the clock configuration you were using ? Cheers

#debugging

Hi all, I use segger ozone to do debugging via RTT it's free download which may be helpful. It does have swo trace and STM32 JTAG configuration inbuilt it may be something to consider. But I work with

#debugging

+ Erwan, Simen, Krzysztof, Andrzej As mentioned in an earlier email (to which you replied without context so I had to start a new thread), RTT does work across reboots without problems, at least on No

#debugging

Hi, thanks for your feedback ! I have a STM32F746ZE-based board and using west with jlink runner to flash it. I have the same issue when I reset the target via JLink Commander.

#debugging

Hi there, We don’t use SWO but RTT (also from Segger) and we don’t need to reset the JLinkRTTViewer/Logger when we reset the target. Could it be that the way Zephr flashes and then resets the target (

#debugging

I am still struggling to figure out why I cannot keep receiving traces through reboots. On the same dev board with FreeRTOS it was consistent: I was able to log target resets without re-launching swov

#debugging

Replying to my own issue: First I misunderstood module registration: #include <logging/log.h> // Must be done outside the function LOG_MODULE_REGISTER(toto, LOG_LEVEL_DBG); void main(void) { //... LOG

#debugging

Hi, I am just getting started with Zephyr and currently working on a STM32F746ZE. I added a custom configuration for this board based on STM32F746G_DISCO. After having run successfully the blinky exam

#debugging

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

#debugging #eclipse #gdb

Hello, I am trying to setup Eclipse with GNU MCU Eclipse plugin as an IDE debugger for Zephyr under Ubuntu 19.04. That is mainly in hopes to be able to debug with multiple threads, since I can't seem

#debugging #eclipse #gdb