boards: doc: add more .. zephyr:board-supported-runners::

Catch up on some of the boards recently added as well as some that were
missed in the previous batch update.

Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>

boards/ambiq/apollo3_evb/doc/index.rst

@@ -26,6 +26,8 @@ Supported Features
 Programming and Debugging
 =========================
 
+.. zephyr:board-supported-runners::
+
 Flashing an application
 -----------------------
 

boards/ambiq/apollo3p_evb/doc/index.rst

@@ -26,6 +26,8 @@ Supported Features
 Programming and Debugging
 =========================
 
+.. zephyr:board-supported-runners::
+
 Flashing an application
 -----------------------
 

boards/ambiq/apollo4p_blue_kxr_evb/doc/index.rst

@@ -28,6 +28,8 @@ Supported Features
 Programming and Debugging
 =========================
 
+.. zephyr:board-supported-runners::
+
 Flashing an application
 -----------------------
 

boards/ambiq/apollo4p_evb/doc/index.rst

@@ -27,6 +27,8 @@ Supported Features
 Programming and Debugging
 =========================
 
+.. zephyr:board-supported-runners::
+
 Flashing an application
 -----------------------
 

boards/espressif/esp32s3_eye/doc/index.rst

@@ -135,6 +135,8 @@ below to retrieve those files.
 Building & Flashing
 *******************
 
+.. zephyr:board-supported-runners::
+
 Simple boot
 -----------
 

boards/kws/pico2_spe/doc/index.rst

@@ -42,6 +42,8 @@ The default pin mapping is unchanged from the Pico-SPE.
 Programming and Debugging
 *************************
 
+.. zephyr:board-supported-runners::
+
 As with the Pico-SPE, the SWD interface can be used to program and debug the
 device, e.g. using OpenOCD with the `Raspberry Pi Debug Probe <https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html>`_ .
 

boards/kws/pico_spe/doc/index.rst

@@ -82,6 +82,8 @@ devices as well as both PIO devices).
 Programming and Debugging
 *************************
 
+.. zephyr:board-supported-runners::
+
 Flashing
 ========
 

boards/lilygo/tdongle_s3/doc/index.rst

@@ -54,6 +54,8 @@ below to retrieve those files.
 Building & Flashing
 *******************
 
+.. zephyr:board-supported-runners::
+
 Simple boot
 ===========
 

boards/lilygo/ttgo_tbeam/doc/index.rst

@@ -51,6 +51,8 @@ below to retrieve those files.
 Building & Flashing
 *******************
 
+.. zephyr:board-supported-runners::
+
 Simple boot
 ===========
 

boards/nuvoton/numaker_m2l31ki/doc/index.rst

@@ -32,6 +32,9 @@ More details about the supported peripherals are available in `M2L31 TRM`_
 
 Building and Flashing
 *********************
+
+.. zephyr:board-supported-runners::
+
 Flashing
 ========
 

boards/nuvoton/numaker_m55m1/doc/index.rst

@@ -33,6 +33,9 @@ More details about the supported peripherals are available in `M55M1 TRM`_
 
 Building and Flashing
 *********************
+
+.. zephyr:board-supported-runners::
+
 Flashing
 ========
 

boards/nuvoton/numaker_pfm_m467/doc/index.rst

@@ -35,6 +35,9 @@ More details about the supported peripherals are available in `M460 TRM`_
 
 Building and Flashing
 *********************
+
+.. zephyr:board-supported-runners::
+
 Flashing
 ========
 

boards/nxp/frdm_mcxa166/doc/index.rst

@@ -62,6 +62,8 @@ LPUART 2 is configured as UART for the console.
 Programming and Debugging
 *************************
 
+.. zephyr:board-supported-runners::
+
 Build and flash applications as usual (see :ref:`build_an_application` and
 :ref:`application_run` for more details).
 

boards/nxp/frdm_mcxa276/doc/index.rst

@@ -109,6 +109,11 @@ Connect a USB cable from your PC to J15, and use the serial terminal of your cho
 - Parity: None
 - Stop bits: 1
 
+Programming and Debugging
+=========================
+
+.. zephyr:board-supported-runners::
+
 Flashing
 ========
 

boards/nxp/imx8mm_evk/doc/index.rst

@@ -66,6 +66,8 @@ CPU's UART4. This is used for the M4 and A53 core targets.
 Programming and Debugging (A53)
 *******************************
 
+.. zephyr:board-supported-runners::
+
 U-Boot "cpu" command is used to load and kick Zephyr to Cortex-A secondary Core, Currently
 it is supported in : `Real-Time Edge U-Boot`_ (use the branch "uboot_vxxxx.xx-y.y.y,
 xxxx.xx is uboot version and y.y.y is Real-Time Edge Software version, for example

boards/nxp/imx8mp_evk/doc/index.rst

@@ -62,6 +62,8 @@ CPU's UART4.
 Programming and Debugging (A53)
 *******************************
 
+.. zephyr:board-supported-runners::
+
 U-Boot "cpu" command is used to load and kick Zephyr to Cortex-A secondary Core, Currently
 it is supported in : `Real-Time Edge U-Boot`_ (use the branch "uboot_vxxxx.xx-y.y.y,
 xxxx.xx is uboot version and y.y.y is Real-Time Edge Software version, for example

boards/nxp/imx93_evk/doc/index.rst

@@ -116,6 +116,8 @@ Note: The overlay only supports ``mimx9352/a55``, but can be extended to support
 Programming and Debugging (A55)
 *******************************
 
+.. zephyr:board-supported-runners::
+
 U-Boot "cpu" command is used to load and kick Zephyr to Cortex-A secondary Core, Currently
 it is supported in : `Real-Time Edge U-Boot`_ (use the branch "uboot_vxxxx.xx-y.y.y,
 xxxx.xx is uboot version and y.y.y is Real-Time Edge Software version, for example

boards/nxp/imx95_evk/doc/index.rst

@@ -113,6 +113,8 @@ The first ENET1 port could be enabled for M7 by west build option
 Programming and Debugging (A55)
 *******************************
 
+.. zephyr:board-supported-runners::
+
 Use this configuration to run basic Zephyr applications and kernel tests,
 for example, with the :zephyr:code-sample:`synchronization` sample:
 

boards/olimex/olimexino_stm32/doc/index.rst

@@ -351,6 +351,8 @@ The default jumper settings for the OLIMEXIMO-STM32E are:
 Flashing Zephyr onto OLIMEXINO-STM32
 ************************************
 
+.. zephyr:board-supported-runners::
+
 Flashing the Zephyr kernel onto OLIMEXINO-STM32 requires the
 `stm32flash tool`_.
 

boards/others/serpente/doc/index.rst

@@ -46,6 +46,8 @@ to the host PC.
 Programming and Debugging
 =========================
 
+.. zephyr:board-supported-runners::
+
 The Serpente ships the BOSSA compatible UF2 bootloader. The bootloader
 can be entered by quickly tapping the reset button twice.
 

boards/rakwireless/rak11720/doc/index.rst

@@ -42,6 +42,8 @@ Supported Features
 Programming and Debugging
 =========================
 
+.. zephyr:board-supported-runners::
+
 The RAK11720 board shall be connected to a Segger Embedded Debugger Unit
 `J-Link OB <https://www.segger.com/jlink-ob.html>`_. This provides a debug
 interface to the Apollo3 Blue chip. You can use JLink to communicate with

boards/rakwireless/rak3172/doc/index.rst

@@ -43,6 +43,8 @@ Supported Features
 Programming and Debugging
 =========================
 
+.. zephyr:board-supported-runners::
+
 The RAK3172 board can be debugged and flashed with an external debug probe connected
 to the SWD pins.
 It can also be flashed via `pyOCD`_, but have to install an additional pack to support STM32WL.

boards/renesas/rzt2m_rsk/doc/index.rst

@@ -62,6 +62,8 @@ The Zephyr console uses UART0.
 Programming and Debugging
 *************************
 
+.. zephyr:board-supported-runners::
+
 Applications for the ``rzt2m_rsk`` board can be built in the usual way as
 documented in :ref:`build_an_application`.
 

boards/sensry/ganymed_bob/doc/index.rst

@@ -64,6 +64,8 @@ For more detailed description please refer to `Ganymed BreakOut Board Documentat
 Programming and Testing
 ***********************
 
+.. zephyr:board-supported-runners::
+
 Building
 ========
 

boards/sensry/ganymed_sk/doc/index.rst

@@ -64,6 +64,8 @@ For more detailed description please refer to `Ganymed StarterKit Board Document
 Programming and Testing
 ***********************
 
+.. zephyr:board-supported-runners::
+
 Building
 ========
 

boards/silabs/dev_kits/sltb010a/doc/index.rst

@@ -89,6 +89,8 @@ board.
 Programming and Debugging
 =========================
 
+.. zephyr:board-supported-runners::
+
 Flashing an application
 -----------------------
 

boards/silabs/dev_kits/xg27_dk2602a/doc/index.rst

@@ -81,6 +81,8 @@ Commander in unattended mode and passes all the necessary arguments to it.
 Programming and Debugging
 =========================
 
+.. zephyr:board-supported-runners::
+
 The sample application :zephyr:code-sample:`hello_world` is used for this example.
 Build the Zephyr kernel and application:
 

boards/st/steval_stwinbx1/doc/index.rst

@@ -256,7 +256,9 @@ There are two possible options for Zephyr console output:
 Console default settings are 115200 8N1.
 
 Programming and Debugging
--------------------------
+*************************
+
+.. zephyr:board-supported-runners::
 
 There are two alternative methods of flashing ST Sensortile.box Pro board:
 
@@ -297,7 +299,7 @@ It is recommended to use the latest version of `STM32CubeProgrammer`_
 
 
 Flash an Application to STEVAL-STWINBX1
-------------------------------------------
+---------------------------------------
 
 There are two ways to enter DFU mode:
 

boards/st/stm32mp135f_dk/doc/index.rst

@@ -108,6 +108,8 @@ Memory mapping
 Programming and Debugging
 *************************
 
+.. zephyr:board-supported-runners::
+
 Prerequisite
 ============
 

boards/ti/msp_exp432p401r_launchxl/doc/index.rst

@@ -36,6 +36,8 @@ More details about the supported peripherals are available in MSP432P4XX TRM.
 Building and Flashing
 *********************
 
+.. zephyr:board-supported-runners::
+
 Prerequisites:
 ==============
 

boards/vcc-gnd/yd_stm32h750vb/doc/index.rst

@@ -42,6 +42,8 @@ is driven by the PLL clock at 480MHz. PLL clock is feed by a 25MHz high speed ex
 Flashing
 ========
 
+.. zephyr:board-supported-runners::
+
 There are 2 main entry points for flashing STM32H750VB SoCs, one using the ROM
 bootloader, and another by using the SWD debug port (which requires additional
 hardware such as ST-Link). Flashing using the ROM bootloader requires a special activation

boards/we/ophelia4ev/doc/index.rst

@@ -26,6 +26,8 @@ Supported Features
 Programming and Debugging
 *************************
 
+.. zephyr:board-supported-runners::
+
 Applications for the ``ophelia4ev/nrf54l15/cpuapp`` board target can be
 built, flashed, and debugged in the usual way. See
 :ref:`build_an_application` and :ref:`application_run` for more details on