Skip to main content
Associate III
Oct 13, 2026 5:41 AM UTC
Question

STM32MP257F-EV1 stopped booting after MDF1/SAI2 rework: rails OK, NRST OK, no Boot ROM UART or USB response

Product / board: STM32MP257F-EV1, MB1936 revision, configuration [A35-TD or M33-TD]

Summary
The board worked for one session after two hardware changes, then stopped booting. LD6, LD5 and LD11 light. LD3 and LD4 do not. The Boot ROM gives no response over UART or USB.

What was changed

  • A PDM microphone was wired to PA6/PA7 by a wire tap at R169/R175 (MDF1). This was our own design decision, not based on any ST recommendation.
  • A MAX98357A speaker amplifier was added on SAI2A (PJ11, PJ3, PJ12 at AF4), with matching device-tree changes.

What I have checked

Check Result
NRST (B1) 3.3 V idle, 0 V pressed, 3.3 V after release
VDDIO 3.3 V
1V8 1.8 V
VDDCPU 0.8 V
VDDCORE 0.8 V
VDDGPU 0 V (not treated as a fault)
VDD_DDR 0.037 V (not treated as a fault)
VDDA1V8_AON 1.8 V 
VDD3V3USB 3.3 V 
HSE Not checked; no accessible probe point

Boot ROM tests (SW1 all OPEN)

  • STM32_Programmer_CLI -l detects the ST-LINK V3.
  • -c port=/dev/ttyACM0 br=115200 and -c port=/dev/ttyACM1 br=115200 both open and then fail: “Timeout error occured while waiting for acknowledgement. Error: Activating device: KO.”
  • With USB DRD connected, no DFU device enumerates on the host.

Not yet done
Peripherals disconnected (mic wires, MAX98357A, speaker); boot of an unmodified ST sample microSD image.

Questions

  1. The main rails and NRST look normal, but the Boot ROM gives no UART acknowledgement and no USB enumeration. What could cause this on the EV1?
  2. Could the PA6/PA7 tap (shared with ETH3 TXD0/TXD1) or the SAI2 wiring interfere with Boot ROM serial download?
  3. Is there a recommended recovery procedure, or a test point for the HSE clock?

Thanks & Regards,

Radha

5 replies

PatrickF
ST Employee
Oct 19, 2026 4:04 PM UTC

Hi ​@Radha Kadam 

After reset, with BOOT[3:0] = all open or close (0b0000 or 0b1111), without any USB DRD connected, you are in serial boot waiting an USB DFU or UART connection. The LD1 (red) should blink fast until connection is done.

After reset, same with BOOT[3:0] = 0b0001 (SD-Card boot, 0 = open, 1 = close) without SD-Card in the slot, fallback to serial boot (USB DFU or UART).

 

After reset, with BOOT[3:0] = 0b0011 or 0b1100, the board is in ‘Development boot’. LD1 (red) should light fixed. No USB enumeration, this mode is intended for JTAG debugging only. This mode only use internal oscillators, so HSE issue cannot block.

 

If none of above work, I fear the board has been damaged (soldering, shortcut, ESD, common mode voltage with external boards, etc...). 

 

If above work, please check again your setup (e.g. bad USB cable which does not have data, only for charging).

 

Regards.


 

In order to give better visibility on the answered topics, please click on 'Best Answer' on the reply which solved your issue or answered your question.Tip of the day: Try Sidekick STM32 AI agent
Associate III
Oct 23, 2026 12:34 PM UTC

Development boot (1100) works: LD1 steady, SWD/JTAG fully functional, A35 halts. The HSE starts and HSERDY sets when enabled by debug writes. In serial boot (0000 and 1111) and in SD boot without a card (0001), LD1 never blinks. What does the Boot ROM depend on in serial boot, before it blinks LD1, that development boot does not use?

Associate III
Oct 23, 2026 12:56 PM UTC

Hello ST Team,

Thank you for the boot-mode guidance. We ran the tests you suggested. Setup: power from CN20 (JP4 [2-3]), JP3 removed, no USB DRD cable, no SD card.

1. LD1 by boot mode

BOOT[3:0] (1 = closed) Mode LD1
0000 Serial boot Not blinking [off / steady on]
1111 Serial boot Not blinking [off / steady on]
0001, no SD card SD boot, fallback to serial Not blinking [off / steady on]
1100 Development boot Steady on (as expected)

2. Debug in development boot (OpenOCD from STM32CubeIDE 2.1.1, stlink-dap)

  • SWD DPIDR 0x6BA02477.
  • stm32mp25x.ap0 and stm32mp25x.axi: Examination succeed. The A35 reports 6 breakpoints and 4 watchpoints.
  • The A35 halts correctly (pc 0x20006000).
  • In serial and SD boot modes, by contrast, AP examination fails: the AP IDRs read, but CSW/BASE are not accessible.

3. HSE check through debug (development boot)

  • Initially: RCC_OCENSETR (0x4420049C) = 0x1 and RCC_OCRDYR (0x442004A4) = 0x1 (HSI only).
  • After writing HSEON (0x100 to RCC_OCENSETR): RCC_OCRDYR = 0x101. HSERDY sets and stays set after 2 s.
  • The 40 MHz HSE crystal (X2, NX1612SA) starts and runs.

4. Boot ROM UART RX pins in serial boot (SW1 0000, ST-LINK [powered / not powered])

Pin UART Voltage
PA8 USART2 RX 1.9 V, slowly falling to 0.3 V (appears floating)
PB15 UART5 RX 0 V
PF4 USART6 RX 0.8 V
PF3 UART8 RX 0.8 V
PB14 UART9 RX 0 V

5. Earlier results (summary)

  • Rails OK: VDDIO 3.3 V, 1V8 1.8 V, VDDCPU 0.8 V, VDDCORE 0.8 V, VDDA1V8_AON 1.8 V, VDD3V3USB 3.3 V.
  • NRST normal; supply current 80 mA at 5 V.
  • PA6/PA7 SoC pins and the other ETH3 TX pins: 0.627 V in diode mode, so no pin damage. R169/R175 restored to 22 Ω.
  • Serial boot: no USB DFU device and no Boot ROM UART acknowledgement on either ST-LINK VCP port.
  • TP13 (BOOTFAILN) stays at 3.3 V. No OTP or PMIC NVM programming has ever been done.

Our interpretation
The SoC, the HSE and the boot-pin sampling all work, since development boot is fully functional. The Boot ROM fails only in serial and SD-fallback boot, before LD1 starts blinking. We suspect the floating PA8 (USART2 RX) line is seen as UART activity, so the Boot ROM locks onto that UART and stops scanning USB. We have not yet confirmed this.

Questions

  1. In serial boot, can a floating or low UART RX line (PA8, PB15 or PB14) stop LD1 blinking and block USB DFU detection?
  2. On the MB1936, what should drive PA8 when idle: the ST-LINK VCP TX, or a pull-up? What voltage should we expect there in serial boot?
  3. Apart from the UART RX lines, what else does the Boot ROM depend on in serial boot, before blinking LD1, that development boot does not use (for example the USB PHY supplies)?
  4. Since debug works in development boot, can we recover by loading TF-A into internal RAM over JTAG and running the USB programming service?

Best regards,
Radha

Associate III
Oct 26, 2026 7:03 AM UTC

Hello ​@PatrickF,

Thank you for the boot-mode guidance. Here are the results of the tests you suggested, plus some follow-up checks. Setup: CN20 power (JP4 [2-3]), JP3 removed, no SD card, no USB DRD cable.

1. LD1 by boot mode

BOOT[3:0] (1 = closed) Mode LD1
0000 Serial boot Not blinking [off / steady on]
1111 Serial boot Not blinking [off / steady on]
0001, no SD card SD boot, fallback to serial Not blinking [off / steady on]
1100 Development boot Steady on

2. Debug in development boot (OpenOCD, STM32CubeIDE 2.1.1)

  • ap0, the A35 and axi: Examination succeed.
  • The A35 halts normally (pc 0x20006000), and memory reads work.

3. HSE check through JTAG (development boot)

  • Initially, RCC_OCENSETR = 0x1 and RCC_OCRDYR = 0x1 (HSI only).
  • After setting HSEON, RCC_OCRDYR = 0x101: HSERDY sets and stays set.
  • The 40 MHz HSE (X2) works.

4. Serial boot measurements (SW1 0000, ST-LINK connected)

Signal Reading
STLINK_VCP1_TX (ST-LINK to MP257), both ends 3.3 V, steady
ETH2.NRST (PG6) 0 V (ETH2 PHY in reset)
ETH3 PHY reset 3.3 V (ETH3 PHY running)
PA8 = USART2 RX, shared with ETH3.RXD0 0 V

 

Our observation
Development boot works and the HSE is good, but serial boot never blinks LD1. In serial boot the ETH3 PHY is out of reset, and PA8 (USART2 RX) is held low.

We cannot make hardware modifications to the board.

Questions

  1. Are “ETH3 PHY reset high” and “PA8 = 0 V” the expected levels on the MB1936 during serial boot?
  2. Can a low level on PA8 make the Boot ROM select USART2 and block USB DFU and the LD1 blinking?
  3. Since JTAG works in development boot, is there a supported software-only recovery, for example loading TF-A over JTAG to run the USB programming service? If so, please share the steps.
  4. If not, please advise on the replacement or RMA process.

Best regards,

PatrickF
ST Employee
Oct 27, 2026 3:38 PM UTC

Hi,
I’m puzzle with PA8 low or floating as there is a pull-up to VDDIO (R107).
Similarly, ETH1.NRST (used for ETH1 and ETH3) and ETH2.NRST (for ETH2) have both a pull-down (R206 and R205). They should be low when no SW is running.


If UART_RX pin is floating, there is a small risk that BootROM in serial boot mode could detect a 0x7F (the first expected byte, used for autobaud) due to noise on the line and wait for further UART connection data. But I never see such issue (I don’t have details, but there might be additional BootROM serial protocol protection to avoid that issue). 
We recommend UART RX pull-up mostly because with RX line stuck to 0, uBoot could detect a ‘line break’ and stop the boot procedure, going to prompt.

 

For a board replacement, please contact the vendor from whom you purchased the board. The warranty may be void if the board has been modified.

 

Regards.

In order to give better visibility on the answered topics, please click on 'Best Answer' on the reply which solved your issue or answered your question.Tip of the day: Try Sidekick STM32 AI agent