Setup differences between STM32MP2 and STM32MP1 devices

This page summarizes the key differences in the STM32MP2 setup compared to the STM32MP1 setup that is described here.

1. As of March 2025, the running envsetup.sh gives an optional choice to review the EULA. If you do not proceed to reviewing (and accepting) it, the build process will produce incomplete SD card images that would cause a kernel panic in the etnaviv module:

   [ 8.531340] etnaviv etnaviv: bound 48280000.gpu (ops gpu_ops [etnaviv])
   E/TC:1 0 Panic at /usr/src/debug/optee-os-stm32mp/4.0.0-stm32mp-r1/core/drivers/clk/clk-stm32mp25.c:1976 <clk_stm32_pll_init>
   E/TC:1 0 TEE load address @ 0x82000000
   E/TC:1 0 Call stack:
   

   You can resolve the crash by manually deleting etnaviv.ko, however, it is easier to ensure that the EULA is accepted prior to running bitbake:

   

2. Programming the SD card via the ST-Link programmer tool requires a USB-PD cable (USB-C to USB-C) attached to the power connector. A regular USB-A to USB-C cable can be used for the data connection:
3. The default target hostname for the openstlinux-6.6-yocto-scarthgap-mpu-v24.12.05 release is stm32mp2-e3-ac-25. The default user name is root with an empty password:

You can download pre-built Windows and Linux toolchains for STM32MP2 devices from our Github repository.