Skip to main content
cfilipescu
Senior
December 17, 2021
Solved

When updating from arm-trusted-firmware-v2.4-stm32mp-r1 to arm-trusted-firmware-v2.4-stm32mp-r2 I get PANIC on UART

  • December 17, 2021
  • 22 replies
  • 14730 views

I didn't change anything in the device tree just compiled the arm-trusted-firmware-v2.4-stm32mp-r2 instead of arm-trusted-firmware-v2.4-stm32mp-r1 and I get the following on UART:

PANIC at PC : 0x2ffcfd2b

What is different between the two versions?

Best answer by Bernard PUEL

You can do this simple test:

in tf-a dts (only in tf-a), remove this line: vmmc-supply = <&v3v3>;

It will remove the switch off/on of buck4 during sdmmc init.

Please let me know if it can solve the issue on your board. Dev team is thinking about a better correction .....

22 replies

GHers.1
Associate
May 26, 2025

Hello Bernard,

As I understand, the line vmmc-supply = <&v3v3> connects the supply v3v3 to the alias vmmc-supply, and the TF-A uses this alias to toggle the v3v3 supply. This toggling is not allowing the eMMC to respond correctly to CMD13 (SDMMC init), because it takes time for the supply to become stable after the toggle.

Am I correct here?

We use this line in the eMMC Flash node.

Is the same toggling done also for vqmmc-supply = <&v3v3>?

Shouldn't we also avoid doing that in the TF-A?

thank you

Gil

GHers.1
Associate
June 4, 2025

Hello Bernard,

I'd highly appreciate if you can answer my message above.

thank you

Gil