Showing results for 
Search instead for 
Did you mean: 

STM32MP1 bring-up troubleshooting guide

If It is the first time the boot chain is starting but fails, please see the classical pitfall below to get help

You can also visit the FAQ STM32MP1 bring-up procedure to have more information on how to start. 
Other resources: STM32MPU forum
STM32MPU knowledge base: 


1. Classical pitfall


  • only PANIC lines appears in console 
ex : PANIC at PC : 0x2ffdf9ef
       Exception mode=0x00000016 at: 0x2ffda000
-Check HSE source configuration issue

ROM CODE makes auto detection of the HSE configuration (crystal or oscillator).

If TF-A reconfigures wrongly it can stop after reconfiguration.


-Check configuration I2Cbus connection to STPMIC
I2C bus for pmic is done at early phase and raises a panic when the bus fails to be enabled.
In OpenSTLinux by default, TF-A expects STPMIC on I2C4. If this is not the case on your design device tree and TF-A code have to be modified. 



2. What to do if ROM Code does not answer to STM32CubeProgrammer ?

Symptoms:  no MP1 USB profile returned upon host PC at enumeration

Check connection serial boot interface pins in PCB of UART or USB-OTG
Check the internal state of the ROMcode with PA13 pin :

- PA13 is open-drain toggling slow (~5Hz) when BootROM is waiting USB/Serial connection
- PA13 is open-drain toggling fast (~5kHz) on engineering Boot
- PA13 is not toggling (i.e. Hi-z) if successful detection of FSBL from Flash
- PA13 is obviously not toggling if MP1 is maintained in Reset whatever the cause, NRST or NRST_CORE low, VDD or VDDCORE too low.


Check If MP1 is not maintained under reset

Check if the voltage on VDD_CORE, VDD

Check the NRST NRST_CORE level, should be high
Check if PWR_ON level, should be high

3. Wrong TF-A binary on serial

Since 2.X there are 2 TF-A binaries:
 one to boot from serial link with USB/UART stack to interact with CubeProg
 one to boot from flash device. It does not content serial stacks (USB,UART) to save space.
Since 3.X, one TF-A binary is compiled for a given boot device (USB, UART, SD-Card, eMMC,…)
Load TF-A in SYSRAM with STM32CubeProgrammer and Rom code from USB: -c port=usb1 -w ../build/trusted/tf-a-stm32mp157c-displayboard-mx-trusted.stm32 0x01 --start 0x01
NOTICE:  Model: Display Board
WARNING: VDD unknown
INFO:    Reset reason (0x4):

INFO:      Pad Reset from NRST
INFO:    Using USB
INFO:      Instance 2
INFO:    Boot used partition fsbl1
ERROR:   Boot interface 6 not supported
PANIC at PC : 0x2ffd5a99
Exception mode=0x00000016 at: 0x2ffd5a99
Note : In 3.x TF-A code boot_interface_selected = 6 means TF-A compilation  STM32MP_USB_PROGRAMMER flag is not defined.

4. No U-boot trace on console

You only see the last trace of TF-A  : "INFO SP_MIN : Preparing exit to normal world"
-Check the Uboot bottom address in Uboot device tree correspond to the DRAM size of PCB 
The botton address is define in Uboot device tree
Ex for ST EV1 board (8GBits) :
memory@c0000000 {
reg = <0xc0000000 0x40000000>;
More info in
-If boot from UART , Check Uboot .dts that UART is same as UART ROMCode
-check that no pinctrl (for RCC MCO_1 MCO_2 output gpio) are defined in rcc node of the device tree.
For example if you see from a STM32Cube MX generated device tree
&rcc {
    pinctrl-names = "default", "sleep";
    pinctrl-0 = <&rcc_pins_mx>;
    pinctrl-1 = <&rcc_sleep_pins_mx>;
status = "okay";
Add to suppress the pincrtl properties
    /* USER CODE BEGIN rcc */
    /* USER CODE END rcc */

5. Kernel hangs

symptoms : kernel traces are stopped, nothing happen.
-check that no pinctrl (for RCC MCO_1 MCO_2 output gpio) are defined in rcc node of the device tree.

6. Kernel console commands ko , traces ok

symptoms: cannot enter any command into the console, the traces are fine.
in console uart node to switch Uart in interrupt mode 
add     /delete-property/dmas;

7. ​​​Uboot SDCard voltage error

"Loading Environment from EXT4... Card did not respond to voltage select!  "

(Instead of "Loading Environment from EXT4... OK")


This error is when SDCard never responds to Uboot commands.

TF-A boots correctly from SD Card but we cannot access to it from Uboot. Issue might come when sdmmc1 node contains wrong properties in Uboot dts file (power supply/level shifter properties).
Check if sdmmc node is adapted to your PCB design, with or without level shifter:
STM32MP1-SDMMC1 is directly connected to Sdcard socket (DK2 case) ,see as reference DK2 Uboot device sdmmc1 node
STM32MP1-SDMMC1 is connected to SDcard socket via a SDMMC level shifter (EV1 case), see as reference EV1 sdmmc1 node


8. DDR intensive Noise Burst or stress tests fails what to check ?

Check some typical pitfall :

  • Check the track length constraints full-filled in the layout ? Refer to AN5122 to check the of DDR signal lanes length.
  • 24MHz Oscillator, not a crystal/resonator, is highly recommended if the design use LTCD // outputs (See Errata sheet).
  • Supply noise on VDDQ_DDR, DDR_VREF lines.

When DDR tests fail, results should be analyzed to see if fail occur on specific data or address.
A procedure is available in AN5168 §8.4 “Test flow” and §3.4 “PHY timings”.
The DDR settings in CubeMX DDR parameters are described in AN5168.
Impedance on DQ/DQS byte line can be modified AN5168 § 5 and relax timings AN5168 §6 to know
how to change them.
If your PCB layout regarding DRAM-STM32MP1 chipset is picked-up from ST PCB layout examples or from ST boards, DRAM should be successful. Signal integrity tests have been passed on the DRAM-STM32MP1 connexion.

9. Incorrect ecc parameter in  U-boot device tree => wrong SLC NAND flashing done by STM32CubeProgrammer 

Symptoms : ROM code does not start
-Uboot sees all // NAND partition
-CubeProg flash ok but with some "Skipping bad block at 0x07f80000" error message
The NAND is miss programmed by Uboot flash service because Uboot DT
shows properties that are not aligned with the chosen NAND data sheet:
    nand-ecc-strength = <8>; 
    nand-ecc-step-size = <512>;
Further information under :

10ROM Code issue with QUADSPI NAND

Symptom : NAND can be accessed with Uboot but ROM code cannot boot from NAND
- OTP#9 configuration should be set according to NAND data sheet parameters (especially number of plane)
- Check NAND pin connections is compatible of the ROM code Serial NAND pins
- Check TF-A header 
-Check configuration of all the memory pin :  WP#/IO2 and HOLD#/IO3 pins.

11. SLC NAND Bring-up classical pitfall

Uboot hangs at  NAND init
Check NWAIT internal pull-up is present in Uboot DT  

 ROMcode does not start

Check if OTP are virgin
Check pins out, power domain is ON for NAND supply
Check ONFI compatible nand otherwise OTP#9 configuration (see ROM code overwiew wiki article)
Check if NAND is not multiplane (not supported by ROM code)
If RevB Flash ONFI with 1-bit ECC does not work
Check vs mem DS Uboot ecc param in DT for FMC ecc algo selection (for flash Programming , Uboot does not rely on ONFI)


12. Uboot : Mac address not set in OTP -  is it blocking ? No

 Uboot error :
"invalid MAC address in OTP 00:00:00:00:00
stm32_smc: Failed to exec svc=82001003 op=1 in secure mode (err = -3)"

This is not a critical error, but just a warning concerning the fact that the MAC address has not been written in the OTP of your device.
In this condition Linux kernel will use a random MAC address, so we can consider it as a warning only.
U-Boot instead will fail to initialize the Ethernet, so it's an issue only for U-Boot networking.
You can bypass it by setting the MAC address manually at u-boot prompt with the commands
setenv .flags ethaddr
setenv ethaddr 11:22:33:44:55:66
To continue the boot after setting MAC, type run bootcmd

13. Uboot hangs at bring-up when Uboot initalizes SLC NAND

DRAM:  128 MiB
- MPU : 650 MHz
- MCU : 208 MHz
- AXI : 266.500 MHz
- PER : 24 MHz
- DDR : 533 MHz
WDT:   Started with servicing (32s timeout)
NAND:   <<<<<< hangs
Check pin muxing , supply, internal pull-up on NWAIT (see AN5031 for internal pull-up)
Senior III
Community manager
Community manager

Hi @debugging,

The links have now been updated. Thanks for your feedback!

Best regards,

Senior III

clicking on the link

is still broken. the link would be helpful as I am facing the panic issue

A custom board with discrete power (no PMIC) and with crystal osc in hardware. The HSE is configured as crystal osc in CubeMX.  So need to try further. Just after the cubeprogrammer flashes part 0x3 (FIP) panic occurs: The UART output shows:

PANIC at PC : 0x2ffec8f3

Exception mode=0x00000016 at: 0x2ffec8f3


Senior III

Can someone please help to fix the link ?

Community manager
Community manager

Hi @debugging - the author of the Wiki has been notified about the issue.
I am working on finding an earlier version that includes the section you need, to help resolving your issue.

I will get back to you as soon as it's available.

Best regards,

Senior III

One week later..

Senior III

Two weeks later....

Version history
Last update:
‎2023-09-18 02:02 AM
Updated by: