patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 7 Packages Projects Releases Wiki Activity

boards: nucleo_wba52cg: Enable flash and debug using OpenOCD

Browse source 
OpenOCD can now be used to flash and debug nucleo_wba52cg.
However, today, it requires use of recent upstream OpenOCD.
Add instructions on how to proceed.

Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
This commit is contained in:
Erwan Gouriou 2023-05-11 11:22:41 +02:00 committed by Carles Cufí
parent 82b1df21cf
commit b9b3e91dba
2 changed files with 67 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

44
boards/arm/nucleo_wba52cg/doc/nucleo_wba52cg.rst
View file

@ -222,12 +222,32 @@ Default settings are 115200 8N1.
Programming and Debugging
*************************
Nucleo WBA52CG board includes an ST-LINK/V3 embedded debug tool interface.
It could be used for flash and debug using either OpenOCD or STM32Cube ecosystem tools.
OpenOCD Support
===============
For now, openocd support is available only on upstream OpenOCD. You can check
`OpenOCD official Github mirror`_.
In order to use it, you should clone and compile it following usual README
guidelines.
Once it is done, you can set the OPENOCD and OPENOCD_DEFAULT_PATH variables in
:zephyr_file:`boards/arm/nucleo_wba52cg/board.cmake` to point the build
to the paths of the OpenOCD binary and its scripts, before
including the common openocd.board.cmake file:
.. code-block:: none
set(OPENOCD "<path_to_opneocd_repo>/src/openocd" CACHE FILEPATH "" FORCE)
set(OPENOCD_DEFAULT_PATH <path_to_opneocd_repo>/tcl)
include(${ZEPHYR_BASE}/boards/common/openocd.board.cmake)
Flashing
========
Nucleo WBA52CG board includes an ST-LINK/V3 embedded debug tool interface.
For now, only STM32CubeProgrammer is available for flashing. It is configured
as flashing tool by default.
STM32CubeProgrammer is configured as flashing tool by default.
If available OpenOCD could be used. Same process applies with both tools.
Flashing an application to Nucleo WBA52CG
-----------------------------------------
@ -244,6 +264,21 @@ You will see the LED blinking every second.
Debugging
=========
Debugging using OpenOCD
-----------------------
You can debug an application in the usual way using OpenOCD. Here is an example for the
:zephyr:code-sample:`blinky` application.
.. zephyr-app-commands::
:zephyr-app: samples/basic/blinky
:board: nucleo_wba52cg
:maybe-skip-config:
:goals: debug
Debugging using STM32CubeIDE
----------------------------
You can debug an application using a STM32WBA compatible version of STM32CubeIDE.
For that:
- Create an empty STM32WBA project by going to File > New > STM32 project
@ -265,3 +300,6 @@ For that:
.. _STM32WBA52CG reference manual:
https://www.st.com/resource/en/reference_manual/rm0493-multiprotocol-wireless-bluetooth-lowenergy-armbased-32bit-mcu-stmicroelectronics.pdf
.. _OpenOCD official Github mirror:
https://github.com/openocd-org/openocd/commit/870769b0ba9f4dae6ada9d8b1a40d75bd83aaa06

26
boards/arm/nucleo_wba52cg/support/openocd.cfg Normal file
View file

@ -0,0 +1,26 @@
# Note: Using OpenOCD using nucloe_wba52cg requires using STMicroelectronics
# openocd fork. See board documentation for more information
source [find interface/stlink-dap.cfg]
set WORKAREASIZE 0x8000
transport select "dapdirect_swd"
# Enable debug when in low power modes
set ENABLE_LOW_POWER 1
# Stop Watchdog counters when halt
set STOP_WATCHDOG 1
# STlink Debug clock frequency
set CLOCK_FREQ 8000
# Reset configuration
# use hardware reset, connect under reset
# connect_assert_srst needed if low power mode application running (WFI...)
reset_config srst_only srst_nogate
source [find target/stm32wbax.cfg]
gdb_memory_map disable