boards/st/nucleo_h503rb/doc/index.rst
.. zephyr:board:: nucleo_h503rb
Overview
The Nucleo-H503RB board features an ARM® Cortex®-M33 core-based STM32H503RBT6 microcontroller with a wide range of connectivity support and configurations. Here are some highlights of the Nucleo-H503RB board:
STM32H503RB microcontroller featuring 128 Kbytes of Flash memory and 32 Kbytes of SRAM in LQFP64 package
Board connectors:
Flexible board power supply:
On-board ST-LINK/V3EC debugger/programmer:
One user LED shared with ARDUINO® Uno V3
Two push-buttons: USER and RESET
32.768 kHz crystal oscillator
24 MHz HSE crystal oscillator
More information about the board can be found at the NUCLEO_H503RB website_.
.. image:: img/nucleo_h503rb.png :align: center :alt: NUCLEO-H503RB
Hardware
The STM32H503xx devices are a high-performance microcontrollers family (STM32H5 series) based on the high-performance Arm® Cortex®-M33 32-bit RISC core. They operate at a frequency of up to 250 MHz.
Core: Arm® Cortex®-M33 CPU with FPU, MPU, 375 DMIPS (Dhrystone 2.1), and DSP instructions
ART Accelerator
Memories
Clock management
Embedded regulator (LDO)
Up to 49 fast I/Os (most 5 V tolerant), up to 9 I/Os with independent supply down to 1.08 V
Analog peripherals
1x Digital temperature sensor
Up to 11 timers
Up to 16x communication interfaces
Two DMA controllers to offload the CPU
Security
Development support: serial wire debug (SWD) and JTAG interfaces
More information about STM32H533RE can be found here:
STM32H503rb on www.st.com_STM32H503 reference manual_.. zephyr:board-supported-hw::
Nucleo-H503RB board has 8 GPIO controllers. These controllers are responsible for pin muxing, input/output, pull-up, etc.
For more details please refer to STM32H5 Nucleo-64 board User Manual_.
Nucleo H533RE System Clock could be driven by internal or external oscillator, as well as main PLL clock. By default System clock is driven by PLL clock at 240 MHz, driven by an 24 MHz high-speed external clock.
Nucleo H533RE board has up to 3 U(S)ARTs. The Zephyr console output is assigned to USART3. Default settings are 115200 8N1.
In order to test backup SRAM, you may want to disconnect VBAT from VDD_MCU.
You can do it by removing SB38 jumper on the back side of the board.
VBAT can be provided via the left ST Morpho connector's pin 33.
Programming and Debugging
.. zephyr:board-supported-runners::
Nucleo-H503RB board includes an ST-LINK/V3EC embedded debug tool interface. This probe allows to flash the board using various tools.
Applications for the nucleo_h503rb board can be built and
flashed in the usual way (see :ref:build_an_application and
:ref:application_run for more details).
For now, openocd support for stm32h5 is not available on upstream OpenOCD.
You can check OpenOCD official Github mirror.
In order to use it though, you should clone from the customized
STMicroelectronics OpenOCD Github 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/st/nucleo_h563zi/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_openocd_repo>/src/openocd" CACHE FILEPATH "" FORCE)
set(OPENOCD_DEFAULT_PATH <path_to_opneocd_repo>/tcl)
include(${ZEPHYR_BASE}/boards/common/openocd.board.cmake)
The board is configured to be flashed using west STM32CubeProgrammer_ runner,
so its :ref:installation <stm32cubeprog-flash-host-tools> is required.
Alternatively, OpencOCD or pyOCD can also be used to flash the board using
the --runner (or -r) option:
.. code-block:: console
$ west flash --runner openocd $ west flash --runner pyocd
For pyOCD, additional target information needs to be installed which can be done by executing the following commands:
.. code-block:: console
$ pyocd pack --update $ pyocd pack --install stm32h5
Connect the Nucleo-H503RB to your host computer using the USB port.
Then build and flash an application. Here is an example for the
:zephyr:code-sample:hello_world application.
Run a serial host program to connect with your Nucleo board:
.. code-block:: console
$ minicom -D /dev/ttyACM0
Then build and flash the application.
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: nucleo_h503rb :goals: build flash
You should see the following message on the console:
.. code-block:: console
Hello World! nucleo_h503rb/stm32h503xx
You can debug an application in the usual way. Here is an example for the
:zephyr:code-sample:blinky application.
.. zephyr-app-commands:: :zephyr-app: samples/basic/blinky :board: nucleo_h503rb :goals: debug
.. _NUCLEO_H503RB website: https://www.st.com/en/evaluation-tools/nucleo-h503rb
.. _STM32H5 Nucleo-64 board User Manual: https://www.st.com/resource/en/user_manual/um3121-stm32h5-nucleo64-board-mb1814-stmicroelectronics.pdf
.. _STM32H503RB on www.st.com: https://www.st.com/en/microcontrollers-microprocessors/stm32h503rb
.. _STM32H503 reference manual: https://www.st.com/resource/en/reference_manual/rm0492-stm32h503-line-armbased-32bit-mcus-stmicroelectronics.pdf
.. _STM32CubeProgrammer: https://www.st.com/en/development-tools/stm32cubeprog.html
.. _OpenOCD official Github mirror: https://github.com/openocd-org/openocd/
.. _STMicroelectronics OpenOCD Github: https://github.com/STMicroelectronics/OpenOCD/tree/openocd-cubeide-r6