Arduino Portenta H7

Overview

The Portenta H7 enables a wide diversity of applications taking benefit from Computer Vision, PLCs, Robotics controller, High-end industrial machinery and high-speed booting computation (ms).

The board includes an STM32H747XI SoC with a high-performance DSP, Arm Cortex-M7 + Cortex-M4 MCU, with 2MBytes of Flash memory, 1MB RAM, 480 MHz CPU, Art Accelerator, L1 cache, external memory interface, large set of peripherals, SMPS, and MIPI-DSI.

Additionally, the board features:

  • USB OTG FS

  • 3 color user LEDs

More information about the board can be found at the ARDUINO_PORTENTA_H7 website. More information about STM32H747XIH6 can be found here:

Supported Features

The arduino_portenta_h7 board supports the hardware features listed below.

on-chip / on-board
Feature integrated in the SoC / present on the board.
2 / 2
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.
arduino_portenta_h7
@
/

Type

Location

Description

Compatible

CPU

on-chip

ARM Cortex-M4F CPU1

arm,cortex-m4f

ADC

on-chip

STM32 ADC4

st,stm32-adc

CAN

on-chip

STM32H7 series FDCAN CAN FD controller2

st,stm32h7-fdcan

Clock control

on-chip

STM32H7 RCC (Reset and Clock controller)1

st,stm32h7-rcc

on-chip

STM32 HSE Clock1

st,stm32-hse-clock

on-chip

STM32 HSI Clock1

st,stm32h7-hsi-clock

on-chip

Generic fixed-rate clock provider1 2

fixed-clock

on-chip

STM32 LSE Clock1

st,stm32-lse-clock

on-chip

STM32H7 main PLL3

st,stm32h7-pll-clock

on-chip

STM32 Clock multiplexer1

st,stm32-clock-mux

on-chip

STM32 Microcontroller Clock Output (MCO)2

st,stm32-clock-mco

Counter

on-chip

STM32 counters12

st,stm32-counter

DAC

on-chip

STM32 family DAC1

st,stm32-dac

Display

on-chip

STM32 LCD-TFT display controller1

st,stm32-ltdc

DMA

on-chip

STM32 DMA controller (V1)2

st,stm32-dma-v1

on-chip

STM32 BDMA controller1

st,stm32-bdma

on-chip

STM32 DMAMUX controller2

st,stm32-dmamux

Ethernet

on-chip

STM32H7 Ethernet1

st,stm32h7-ethernet

on-board

Generic MII PHY1

ethernet-phy

Flash controller

on-chip

STM32 Family flash controller1

st,stm32-flash-controller

on-board

STM32 QSPI Flash controller supporting the JEDEC CFI interface1

st,stm32-qspi-nor

GPIO & Headers

on-chip

STM32 GPIO Controller11

st,stm32-gpio

I2C

on-chip

STM32 I2C V2 controller4

st,stm32-i2c-v2

I2S

on-chip

STM32H7 I2S controller3

st,stm32h7-i2s

Interrupt controller

on-chip

ARMv7-M NVIC (Nested Vectored Interrupt Controller)1

arm,v7m-nvic

on-chip

STM32 External Interrupt Controller1

st,stm32-exti

IPM

on-chip

STM32 HSEM MAILBOX1

st,stm32-hsem-mailbox

LED

on-board

Group of GPIO-controlled LEDs1

gpio-leds

MDIO

on-chip

STM32 MDIO Controller1

st,stm32-mdio

Memory controller

on-chip

STM32 Battery Backed RAM1

st,stm32-bbram

on-chip

STM32H7 Flexible Memory Controller (FMC)1

st,stm32h7-fmc

on-chip

STM32 Flexible Memory Controller (SDRAM controller)1

st,stm32-fmc-sdram

MIPI-DSI

on-chip

STM32 MIPI DSI host1

st,stm32-mipi-dsi

MMC

on-chip

STM32 SDMMC Disk Access2

st,stm32-sdmmc

MTD

on-chip

STM32 flash memory1

st,stm32-nv-flash

on-board

Fixed partitions of a flash (or other non-volatile storage) memory1

fixed-partitions

PHY

on-chip

This binding is to be used by all the usb transceivers which are built-in with USB IP1

usb-nop-xceiv

on-board

This binding is to be used by all the usb transceivers which are an external ULPI phy1

usb-ulpi-phy

Pin control

on-chip

STM32 Pin controller1

st,stm32-pinctrl

PWM

on-chip

STM32 PWM12

st,stm32-pwm

QSPI

on-chip

STM32 QSPI Controller1

st,stm32-qspi

Reset controller

on-chip

STM32 Reset and Clock Control (RCC) Controller1

st,stm32-rcc-rctl

RNG

on-chip

STM32 Random Number Generator1

st,stm32-rng

RTC

on-chip

STM32 RTC1

st,stm32-rtc

Sensors

on-chip

STM32 family TEMP node for production calibrated sensors with two calibration temperatures1

st,stm32-temp-cal

on-chip

STM32 VBAT1

st,stm32-vbat

on-chip

STM32 VREF+1

st,stm32-vref

Serial controller

on-chip

STM32 USART1 3

st,stm32-usart

on-chip

STM32 UART4

st,stm32-uart

on-chip

STM32 LPUART1

st,stm32-lpuart

SMbus

on-chip

STM32 SMBus controller4

st,stm32-smbus

SPI

on-chip

STM32H7 SPI controller6

st,stm32h7-spi

SRAM

on-chip

Generic on-chip SRAM description1

mmio-sram

Timer

on-chip

ARMv7-M System Tick1

arm,armv7m-systick

on-chip

STM32 timers14

st,stm32-timers

on-chip

STM32 low-power timer (LPTIM)1

st,stm32-lptim

USB

on-chip

STM32 OTGHS controller1

st,stm32-otghs

on-chip

STM32 OTGFS controller1

st,stm32-otgfs

Video

on-chip

STM32 Digital Camera Memory Interface (DCMI)1

st,stm32-dcmi

Watchdog

on-chip

STM32 watchdog1

st,stm32-watchdog

on-chip

STM32 system window watchdog1

st,stm32-window-watchdog

The high precision low speed external (LSE) clock is only fully supported on boards with hardware revision 4.10 or greater. By default the internal source is used; to enable the use of the external oscillator, manually specify the hardware revision at build time (see Building for a board revision for information on how to build for specific revisions of the board).

Applications that intend to use BLE must specify hardware revision at build time.

Currently only BLE is supported on this board, WiFi is not supported.

Fetch Binary Blobs

The board Bluetooth/WiFi module requires fetching some binary blob files, to do that run the command:

west blobs fetch hal_infineon

Note

Only Bluetooth functionality is currently supported.

Resources sharing

The dual core nature of STM32H747 SoC requires sharing HW resources between the two cores. This is done in 3 ways:

  • Compilation: Clock configuration is only accessible to M7 core. M4 core only has access to bus clock activation and deactivation.

  • Static pre-compilation assignment: Peripherals such as a UART are assigned in devicetree before compilation. The user must ensure peripherals are not assigned to both cores at the same time.

  • Run time protection: Interrupt-controller and GPIO configurations could be accessed by both cores at run time. Accesses are protected by a hardware semaphore to avoid potential concurrent access issues.

Building and Flashing

Applications for the arduino_portenta_h7 board should be built per core target, using either arduino_portenta_h7_m7 or arduino_portenta_h7_m4 as the target. See Building an Application for more information about application builds.

Flashing

Installing dfu-util

This board requires dfu-utils for flashing. It is recommended to use at least v0.8 of dfu-util. The package available in debian/ubuntu can be quite old, so you might have to build dfu-util from source.

Flashing an application to STM32H747I M7 Core

First, connect the Arduino Portenta H7 board to your host computer using the USB port to prepare it for flashing. Double tap the button to put the board into the Arduino Bootloader mode. Then build and flash your application.

Here is an example for the Hello World application.

# From the root of the zephyr repository
west build -b arduino_portenta_h7/stm32h747xx/m7 samples/hello_world
west flash

Run a serial host program to connect with your board:

$ minicom -D /dev/ttyACM0

You should see the following message on the console:

Hello World! arduino_portenta_h7

Similarly, you can build and flash samples on the M4 target. For this, please take care of the resource sharing (UART port used for console for instance).

Here is an example for the Blinky application on M4 core.

# From the root of the zephyr repository
west build -b arduino_portenta_h7/stm32h747xx/m4 samples/basic/blinky
west flash