boards/st/stm32h7b3i_dk/doc/index.rst
.. zephyr:board:: stm32h7b3i_dk
Overview
The STM32H7B3I-DK Discovery kit is a complete demonstration and development platform for STMicroelectronics Arm® Cortex®-M7 core-based STM32H7B3LIH6QU microcontroller.
The STM32H7B3I-DK Discovery kit is used as a reference design for user application development before porting to the final product, thus simplifying the application development.
The full range of hardware features available on the board helps users enhance their application development by an evaluation of almost all peripherals (such as USB OTG_HS, microSD, USART, FDCAN, audio DAC stereo with audio jack input and output, camera, SDRAM, Octo-SPI Flash memory and RGB interface LCD with capacitive touch panel). ARDUINO® Uno V3 connectors provide easy connection to extension shields or daughterboards for specific applications.
Important board features include:
STM32H7B3LIH6Q microcontroller featuring 2 Mbytes of Flash memory and 1.4 Mbyte of RAM in BGA225 package
4.3" (480x272 pixels) TFT color LCD module including a capacitive touch panel with RGB interface
Wi-Fi® module compliant with 802.11 b/g/n
USB OTG HS
Audio codec
512-Mbit Octo-SPI NOR Flash memory
128-Mbit SDRAM
2 user LEDs
User and Reset push-buttons
Fanout daughterboard
1x FDCAN
Board connectors
Flexible power-supply options:
On-board STLINK-V3E debugger/programmer with USB re-enumeration capability
More information about the board can be found at the STM32H7B3I-DK website_.
Hardware
The STM32H7B3I Discovery kit provides the following hardware components:
More information about STM32H7B3 can be found here:
STM32H7A3/7B3 on www.st.com_STM32H7A3/7B3/7B0 reference manual_STM32H7B3xI datasheet_.. zephyr:board-supported-hw::
STM32H7B3I Discovery kit has 11 GPIO controllers. These controllers are responsible for pin muxing, input/output, pull-up, etc.
For more details please refer to STM32H7B3I-DK board User Manual_.
The STM32H7B3I Discovery kit features an Arduino Uno V3 connector. Board is configured as follows
UART_1 TX/RX : PA9/PA10 (ST-Link Virtual Port Com)
UART_4 TX/RX : PH13/PH14 (Arduino Serial)
I2C4 SCL/SDA : PD12/PD13 (Arduino I2C, Touchscreen FT5336 with PH2 Interrupt Pin)
SPI2 SCK/MISO/MOSI/NSS : PA12/PB14/PB15/PI0 (Arduino SPI)
LD1 : PG11
LD2 : PG2
USER_PB : PC13
SDMMC D0/D1/D2/D3/CK/CMD/CD : PC8/PC9/PC10/PC11/PC12/PD2/PI8
CANFD RX/TX/WAKE [#]_ : PA11/PA12/PH8
FMC SDRAM :
LTDC :
The STM32H7B3I System Clock can be driven by an internal or external oscillator, as well as by the main PLL clock. By default, the System clock is driven by the PLL clock at 280MHz. PLL clock is fed by a 24MHz high speed external clock.
The STM32H7B3I Discovery kit has up to 10 UARTs. The Zephyr console output is assigned to UART1 which is connected to the onboard STLINK-V3E. Virtual COM port interface default communication settings are 115200 8N1.
Programming and Debugging
.. zephyr:board-supported-runners::
STM32H7B3I Discovery kit includes an STLINK-V3E embedded debug tool interface.
Applications for the stm32h7b3i_dk 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
Flashing may depend on the SoC option bytes configuration, which can be checked and
updated using STM32CubeProgrammer_.
First, connect the STM32H7B3I Discovery kit to your host computer using the USB port to prepare it for flashing. Then build and flash your application.
Here is an example for the :zephyr:code-sample:hello_world application.
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: stm32h7b3i_dk :goals: build flash
Run a serial host program to connect with your board:
.. code-block:: console
$ minicom -D /dev/ttyACM0
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: stm32h7b3i_dk :goals: debug
.. _STM32H7B3I-DK website: https://www.st.com/en/evaluation-tools/stm32h7b3i-dk.html
.. _STM32H7B3I-DK board User Manual: https://www.st.com/resource/en/user_manual/um2569-discovery-kit-with-stm32h7b3li-mcu-stmicroelectronics.pdf
.. _STM32H7A3/7B3 on www.st.com: https://www.st.com/en/microcontrollers-microprocessors/stm32h7a3-7b3.html
.. _STM32H7A3/7B3/7B0 reference manual: https://www.st.com/resource/en/reference_manual/rm0455-stm32h7a37b3-and-stm32h7b0-value-line-advanced-armbased-32bit-mcus-stmicroelectronics.pdf
.. _STM32H7B3xI datasheet: https://www.st.com/resource/en/datasheet/stm32h7b3ai.pdf
.. _STM32CubeProgrammer: https://www.st.com/en/development-tools/stm32cubeprog.html
.. _STM32H7B3I_DK board schematics: https://www.st.com/resource/en/schematic_pack/mb1332-h7b3i-c02_schematic.pdf
.. [#] To use CAN, solder bridges SB3, SB4 and SB5 need to be connected.
Take note that CANFD pins are shared with STMOD+ connector (P1), so please check
STM32H7B3I_DK board schematics_ for possible collisions if using that connector.