boards: st: stm32f429i_disc1: doc: re-work flashing section

The patch modifies the "Programming and Debugging" and "Flashing" sections
to make the documentation clearer and consistent with what is reported for
other ST boards.

Suggested-by: Abderrahmane Jarmouni <git@jarmouni.me>
Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
This commit is contained in:
Dario Binacchi 2024-11-04 14:35:11 +01:00 committed by Anas Nashif
commit ed48de2583

View file

@ -153,6 +153,7 @@ and host OTG operation, but only device mode has been tested with Zephyr at this
Programming and Debugging Programming and Debugging
************************* *************************
The STM32F429I-DISC1 Discovery kit includes a ST-LINK/V2-B embedded debug tool interface.
Applications for the ``stm32f429i_disc1`` board configuration can be built Applications for the ``stm32f429i_disc1`` board configuration can be built
and flashed in the usual way (see :ref:`build_an_application` and and flashed in the usual way (see :ref:`build_an_application` and
:ref:`application_run` for more details). :ref:`application_run` for more details).
@ -160,12 +161,6 @@ and flashed in the usual way (see :ref:`build_an_application` and
Flashing Flashing
======== ========
The STM32F429I-DISC1 Discovery kit includes a ST-LINK/V2-B embedded debug tool interface.
This interface is supported by the openocd version included in Zephyr SDK.
Flashing an application to STM32F429I-DISC1
-------------------------------------------
The board is configured to be flashed using west `STM32CubeProgrammer`_ runner, The board is configured to be flashed using west `STM32CubeProgrammer`_ runner,
so its :ref:`installation <stm32cubeprog-flash-host-tools>` is required. so its :ref:`installation <stm32cubeprog-flash-host-tools>` is required.