Unable to use thread aware debugging with STM32H743ZI #45778
Comments
|
Correct flag name is |
|
Ok, here is the problem: #37516 implemented integrated west runner support for openocd thread info configuration. For that it relied on the command We miss a way to overload this default generic command, either fully, either only overwriting the target handle ( |
erwango
added
area: West
|
Proposal to fix this is to add an openocd runner arg which would overwrite the default openocd script target handle @mbolivar-nordic Would it be fine with you ? |
Yes |
Openocd scripts for STM32H7 SoCs use _CHIPNAME.cpu{0|1} as
target handle.
Specify this thanks to new openocd runner option '-target-handle'.
This is required to allow thread awareness debugging on these targets.
Fixes zephyrproject-rtos#45778
Signed-off-by: Erwan Gouriou <[email protected]>
Openocd scripts for STM32H7 SoCs use _CHIPNAME.cpu{0|1} as
target handle.
Specify this thanks to new openocd runner option '-target-handle'.
This is required to allow thread awareness debugging on these targets.
Fixes #45778
Signed-off-by: Erwan Gouriou <[email protected]>
Openocd scripts for STM32H7 SoCs use _CHIPNAME.cpu{0|1} as
target handle.
Specify this thanks to new openocd runner option '-target-handle'.
This is required to allow thread awareness debugging on these targets.
Fixes zephyrproject-rtos#45778
Signed-off-by: Erwan Gouriou <[email protected]>
Openocd target cyw20829 does not define _TARGETNAME which is used by default by the openocd west runner when using CONFIG_DEBUG_THREAD_INFO. This is similar to the issue previously addressed for STM32H7: Link: zephyrproject-rtos#45778 Signed-off-by: Hakan Jansson <[email protected]>
Openocd target cyw20829 does not define _TARGETNAME which is used by default by the openocd west runner when using CONFIG_DEBUG_THREAD_INFO. This is similar to the issue previously addressed for STM32H7: Link: #45778 Signed-off-by: Hakan Jansson <[email protected]>
Openocd target cyw20829 does not define _TARGETNAME which is used by default by the openocd west runner when using CONFIG_DEBUG_THREAD_INFO. This is similar to the issue previously addressed for STM32H7: (cherry picked from commit 8e4dc4e) Original-Link: zephyrproject-rtos/zephyr#45778 Original-Signed-off-by: Hakan Jansson <[email protected]> GitOrigin-RevId: 8e4dc4e Cr-Build-Id: 8730937883239782945 Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8730937883239782945 Copybot-Job-Name: zephyr-main-copybot-downstream Change-Id: I6ac4c48d9ce139387e9b1039f59dbc3db4077f54 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/zephyr/+/6028802 Tested-by: ChromeOS Prod (Robot) <[email protected]> Commit-Queue: Tristan Honscheid <[email protected]> Reviewed-by: Tristan Honscheid <[email protected]> Tested-by: Tristan Honscheid <[email protected]>
Describe the bug
When attempting to use the
CONFIG_DEBUG_THREAD_INFOconfiguration option for thread aware debugging with the STM32H743ZI develpment board, after runningwest debugan output containing 'cant read "_TARGETNAME": no such variable', followed by "You can't do that when you target is `exec'" is received.If the configuration option is not added to the project's prj.conf file, I am able to use
west debugwithout issue.I have attempted to add
$_TARGETNAME configure -rtos Zephyrto zephyr/boards/arm/nucleo_h743zi/support/openocd.cfg per #37205, to no avail.To Reproduce
The behavior can be seen on the blinky example.
Steps to reproduce the behavior:
Expected behavior
The ability to run openocd debugging with thread awareness using
west debugon the STM32H743ZI development board.Impact
Currently have no other way of debugging with thread awareness in our system, making it difficult to see which thread could be causing various issue including watchdog timer triggers.
Logs and console output
Environment (please complete the following information):
EDIT (@erwango):
Fixed the Kconfig option name
The text was updated successfully, but these errors were encountered: