boards/st/nucleo_f410rb/doc/index.rst
.. zephyr:board:: nucleo_f410rb
Overview
The Nucleo F410RB board features an ARM Cortex-M4 based STM32F410RB MCU with a wide range of connectivity support and configurations. Here are some highlights of the Nucleo F410RB board:
STM32 microcontroller in QFP64 package
Two types of extension resources:
On-board ST-LINK/V2-1 debugger/programmer with SWD connector
Flexible board power supply:
Three LEDs: USB communication (LD1), user LED (LD2), power LED (LD3)
Two push-buttons: USER and RESET
More information about the board can be found at the Nucleo F410RB website_.
Hardware
Nucleo F410RB provides the following hardware components:
More information about STM32F410RB can be found here:
STM32F410RB on www.st.com_STM32F410 reference manual_.. zephyr:board-supported-hw::
Nucleo F410RB Board has 8 GPIO controllers. These controllers are responsible for pin muxing, input/output, pull-up, etc.
.. image:: img/nucleo_f410rb_arduino_top_left.jpg :align: center :alt: Nucleo F410RB Arduino connectors (top left) .. image:: img/nucleo_f410rb_arduino_top_right.jpg :align: center :alt: Nucleo F410RB Arduino connectors (top right) .. image:: img/nucleo_f410rb_morpho_top_left.jpg :align: center :alt: Nucleo F410RB Morpho connectors (top left) .. image:: img/nucleo_f410rb_morpho_top_right.jpg :align: center :alt: Nucleo F410RB Morpho connectors (top right)
For more details please refer to STM32 Nucleo-64 board User Manual_.
Nucleo F410RB System Clock could be driven by an internal or external oscillator, as well as the main PLL clock. By default, the System clock is driven by the PLL clock at 84MHz, driven by an 8MHz high-speed external clock.
Nucleo F410RB board has 3 USARTs. The Zephyr console output is assigned to UART2. Default settings are 115200 8N1.
Programming and Debugging
.. zephyr:board-supported-runners::
Nucleo F410RB board includes an ST-LINK/V2-1 embedded debug tool interface.
Applications for the nucleo_f410rb board configuration can be built and
flashed in the usual way (see :ref:build_an_application and
:ref:application_run for more details).
The board is configured to be flashed using west STM32CubeProgrammer_ runner,
so its :ref:installation <stm32cubeprog-flash-host-tools> is required.
Alternatively, OpenOCD or JLink can also be used to flash the board using
the --runner (or -r) option:
.. code-block:: console
$ west flash --runner openocd $ west flash --runner jlink
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 -b 115200 -D /dev/ttyACM0
Build and flash the application:
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: nucleo_f410rb :goals: build flash
You should see the following message on the console:
.. code-block:: console
$ Hello World! arm
You can debug an application in the usual way. Here is an example for the
:zephyr:code-sample:hello_world application.
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: nucleo_f410rb :maybe-skip-config: :goals: debug
.. _Nucleo F410RB website: https://www.st.com/en/evaluation-tools/nucleo-F410RB.html
.. _STM32 Nucleo-64 board User Manual: https://www.st.com/resource/en/user_manual/dm00105823.pdf
.. _STM32F410RB on www.st.com: https://www.st.com/en/microcontrollers/stm32f410rb.html
.. _STM32F410 reference manual: https://www.st.com/resource/en/reference_manual/dm00180366.pdf
.. _STM32CubeProgrammer: https://www.st.com/en/development-tools/stm32cubeprog.html