|
Suppress line breaks when using LOG_INF etc with RTT and Segger
#debugging
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
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
|
By
Chruściński, Krzysztof
· #2924
·
|
|
Suppress line breaks when using LOG_INF etc with RTT and Segger
#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
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
|
By
justin.leavesley@...
· #2923
·
|
|
C++ support with debug optimiations
#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
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
|
By
mbarrett@...
· #2822
·
|
|
C++ support with debug optimiations
#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
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
|
By
mbarrett@...
· #2811
·
|
|
Debugging Zephyr using no able to stop at specific source line after init.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
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
|
By
ngbk1993@...
· #2351
·
|
|
Debugging Zephyr using no able to stop at specific source line after init.c
#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
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
|
By
ngbk1993@...
· #2334
·
Edited
|
|
Debug probes and setup
#debugging
#gdb
#nrf52480
#ztest
#bluetoothmesh
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
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
|
By
Carles Cufi
· #2210
·
|
|
Debug probes and setup
#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
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
|
By
Erik
· #2209
·
|
|
Enable traces on Serial Wire Output
#debugging
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.
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.
|
By
David K
· #1925
·
|
|
Enable traces on Serial Wire Output
#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
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
|
By
David K
· #1924
·
|
|
Enable traces on Serial Wire Output
#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
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
|
By
Erwan Gouriou
· #1917
·
|
|
Enable traces on Serial Wire Output
#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
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
|
By
William Fish
· #1916
·
Edited
|
|
Enable traces on Serial Wire Output
#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
+ 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
|
By
Carles Cufi
· #1914
·
|
|
Enable traces on Serial Wire Output
#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.
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.
|
By
David K
· #1913
·
|
|
Enable traces on Serial Wire Output
#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 (
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 (
|
By
Carles Cufi
· #1912
·
|
|
Enable traces on Serial Wire Output
#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
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
|
By
David K
· #1911
·
|
|
Enable traces on Serial Wire Output
#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
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
|
By
David K
· #1901
·
|
|
Enable traces on Serial Wire Output
#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
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
|
By
David K
· #1898
·
|
|
Error in services launch sequence
#debugging
#eclipse
#gdb
All I did was to uncheck the "start pyOCD locally"
All I did was to uncheck the "start pyOCD locally"
|
By
fashtop3@...
· #1762
·
|
|
Error in services launch sequence
#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
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
|
By
...
· #1689
·
|