boards/st/stm32h7s78_dk/doc/index.rst
.. zephyr:board:: stm32h7s78_dk
Overview
The STM32H7S78-DK Discovery kit is designed as a complete demonstration and development platform for STMicroelectronics Arm® Cortex®-M7 core-based STM32H7S7L8H6H microcontroller. Here are some highlights of the STM32H7S78-DK Discovery board:
STM32H7S7L8H6H microcontroller featuring 64 Kbytes of Flash memory and 620 Kbytes of SRAM in 225-pin TFBGA package
USB Type-C® Host and device with USB power-delivery controller
SAI Audio DAC stereo with one audio jacks for input/output,
ST MEMS digital microphone with PDM interface
Octo-SPI interface connected to 1Gbit Octo-SPI NORFlash memory device (MX66UW1G45GXDI00 from Macronix)
Hexadeca-SPI interface connected to 256Mbit PSRAM memory device (APS256XXN-OBRx from AP Memory)
10/100-Mbit Ethernet,
Board connectors
Flexible power-supply options
On-board STLINK-V3E debugger/programmer with USB re-enumeration capability:
4 user LEDs
User and reset push-buttons
More information about the board can be found at the STM32H7S78-DK Discovery website_.
Hardware
The STM32H7S7xx devices are a high-performance microcontrollers family (STM32H7 Series) based on the high-performance Arm® Cortex®-M7 32-bit RISC core. They operate at a frequency of up to 600 MHz.
Core: ARM® 32-bit Cortex®-M7 CPU with FPU.
Performance benchmark:
Security
Clock management:
Power management
RTC with HW calendar, alarms and calibration
Up to 152 fast I/Os, most 5 V-tolerant, up to 10 I/Os with independent supply down to 1.08 V
Up to 23 timers, including 2 watchdogs
Memories
Rich analog peripherals (independent supply)
35x communication interfaces
CORDIC for trigonometric functions acceleration
FMAC (filter mathematical accelerator)
CRC calculation unit
Development support: serial wire debug (SWD), JTAG, Embedded Trace Macrocell™
More information about STM32H7S7 can be found here:
STM32H7Sx on www.st.com_STM32H7Sx reference manual_.. zephyr:board-supported-hw::
The STM32HS7 is a SoC with Cortex-M7 architecture. Zephyr provides support for building for Secure firmware.
The BOARD options are summarized below:
+----------------------+-----------------------------------------------+ | BOARD | Description | +======================+===============================================+ | stm32h7s78_dk | For building Secure firmware | +----------------------+-----------------------------------------------+
STM32H7S78-DK Discovery Board has 12 GPIO controllers. These controllers are responsible for pin muxing, input/output, pull-up, etc.
For more details please refer to STM32H7S78-DK Discovery board User Manual_.
STM32H7S78-DK 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 250MHz, driven by 24MHz external oscillator (HSE).
STM32H7S78-DK Discovery board has 2 U(S)ARTs. The Zephyr console output is assigned to USART4. Default settings are 115200 8N1.
STM32H7S78-DK Discovery board has 2 USB Type-C connectors. Currently, only USB port2 (FS) is supported.
STM32H7S78-DK Discovery board has 2 FDCAN bus interfaces.
FDCAN1 is configured but not enabled by default. To enable it, make sure
that i2c1 is disabled, since they share the PB9 pin.
In order to use Ethernet on STM32H7S78-DK, you need to set the JP6 jumper
to PC1 position on the back side of the board.
Programming and Debugging
.. zephyr:board-supported-runners::
STM32H7S78-DK Discovery board includes an ST-LINK/V3E embedded debug tool interface.
The board is configured to be flashed using west STM32CubeProgrammer_ runner,
so its :ref:installation <stm32cubeprog-flash-host-tools> is required.
Here is an example for the :zephyr:code-sample:hello_world application.
Connect the STM32H7S78-DK Discovery to your host computer using the USB port, then 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: stm32h7s78_dk :goals: build flash
You should see the following message on the console:
.. code-block:: console
Hello World! stm32h7s78_dk
If the application size is too big to fit in SoC Flash,
Zephyr :ref:Code and Data Relocation <code_data_relocation> can be used to relocate
the non-critical and big parts of the application to external Flash.
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: stm32h7s78_dk :maybe-skip-config: :goals: debug
Because of the limited amount of SoC Flash (64 Kbytes), you may want to store the application
in external OSPI Flash instead, and run it from there. In that case, the MCUboot bootloader
is needed to chainload the application. A dedicated board variant, ext_flash_app, was created
for this usecase.
:ref:sysbuild makes it possible to build and flash all necessary images needed to run a user application
from external Flash.
The following example shows how to build :zephyr:code-sample:hello_world with Sysbuild enabled:
.. zephyr-app-commands:: :tool: west :zephyr-app: samples/hello_world :board: stm32h7s78_dk/stm32h7s7xx/ext_flash_app :goals: build :west-args: --sysbuild
By default, Sysbuild creates MCUboot and user application images.
For more information, refer to the :ref:sysbuild documentation.
Both MCUboot and user application images can be flashed by running:
.. code-block:: console
west flash
You should see the following message in the serial host program:
.. code-block:: console
*** Booting MCUboot v2.2.0-192-g96576b341ee1 *** *** Using Zephyr OS build v4.3.0-rc2-37-g6cc7bdb58a92 *** I: Starting bootloader I: Bootloader chainload address offset: 0x0 I: Image version: v0.0.0 I: Jumping to the first image slot *** Booting Zephyr OS build v4.3.0-rc2-37-g6cc7bdb58a92 *** Hello World! stm32h7s78_dk/stm32h7s7xx/ext_flash_app
To only flash the user application in the subsequent builds, Use:
.. code-block:: console
west flash --domain hello_world
With the default configuration, the board uses MCUboot's Swap-using-offset mode.
To get more information about the different MCUboot operating modes and how to
perform application upgrade, refer to MCUboot design.
To learn more about how to secure the application images stored in external Flash,
refer to MCUboot Encryption.
You can debug the application in external flash using west and GDB.
After flashing MCUboot and the app, execute the following command:
.. code-block:: console
west debugserver
Then, open another terminal (don't forget to activate Zephyr's environment) and execute:
.. code-block:: console
west attach
By default, user application symbols are loaded. To debug MCUboot application, launch:
.. code-block:: console
west attach --domain mcuboot
.. _STM32H7S78-DK Discovery website: https://www.st.com/en/evaluation-tools/stm32h7s78-dk.html
.. _STM32H7S78-DK Discovery board User Manual: https://www.st.com/resource/en/user_manual/um3289-discovery-kit-with-stm32h7s7l8-mcu-stmicroelectronics.pdf
.. _STM32H7Sx on www.st.com: https://www.st.com/en/evaluation-tools/stm32h7s78-dk.html
.. _STM32H7Sx reference manual: https://www.st.com/resource/en/reference_manual/rm0477-stm32h7rx7sx-armbased-32bit-mcus-stmicroelectronics.pdf
.. _STM32CubeProgrammer: https://www.st.com/en/development-tools/stm32cubeprog.html
.. _MCUboot design: https://docs.mcuboot.com/design.html
.. _MCUboot Encryption: https://docs.mcuboot.com/encrypted_images.html