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

[cfilipescu]

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?

[GHers.1]

Hello Bernard,

We are using Dunfell V3.1.

According to the thread above, the patch directs to drivers/regulator/regulator_core.c in project arm-trusted-firmware-v2.4-stm32mp-r1 (or r2).

However, in our project, we have this path: 

./arm-trusted-firmware-2.4/drivers/st/regulator/stm32mp_regulator.c

Is this the right path for the file in the patch?

Please advise.

thanks,

Gil

[Bernard PUEL]

Hello Gil,

the proposed patch is in the core part of the regulator (then not specific to stm32 device) so should be no issue to apply it on your release.

Please see the architecture from wiki V3 documentation: https://wiki.st.com/stm32mpu-ecosystem-v3/wiki/Regulator_overview

[GHers.1]

hello Bernard,

I am replying to you just now, since we are trying now to fix the issue now.

In-case we are not able to apply the patch, there is a solution you originally suggested (before the patch was available):

In our case, our custom board connects v3v3 (BUCK4) to both vmmc and vqmmc supplies.

Should I remove both lines (vmmc-supply = <&v3v3>; vqmmc-supply = <&v3v3>) from the TF-A dts?

thanks,

Gil

[Bernard PUEL]

Hello Gil,

The goal was to avoid a new switch off/on of the sdcard (just after the Rom code one). So only vmmc-supply.

[GHers.1]

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.

Might removing also vqmmc-supply = <&v3v3> cause an issue of accessing the eMMC memory?

thank you

Gil

[GHers.1]

Hello Bernard,

We used the workaround of removing vmmc-supply = <&v3v3> from the TF-A dts.

As a result, flashing the TF-A and UBOOT is not happening.

Furthermore, we are unable to flash the previous images.

Do you know why?

How can we revert those changes?

thanks,

Gil