cancel
Showing results for 
Search instead for 
Did you mean: 

STM32MP157 hangs at INFO: SP_MIN: Preparing exit to normal world while exiting standby mdoe

rishi2
Associate III

When exiting out of standby mode through RTC,Wakeup pins or PON Key in all the cases System stops at : INFO:  SP_MIN: Preparing exit to normal world.

Here is the complete log :

[  32.488278] usb33: supplied by vdd_usb

#echo mem > /sys/power/state

[  37.576569] PM: suspend entry (deep)

[  37.587289] Filesystems sync: 0.008 seconds

[  37.591188] Freezing user space processes ... (elapsed 0.001 seconds) done.

[  37.597870] OOM killer disabled.

[  37.601128] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.

[  37.608535] printk: Suspending console(s) (use no_console_suspend to debug)

NOTICE: CPU: STM32MP157C?? Rev.Z

NOTICE: Model: SBS MOBIO

INFO:  Reset reason (0x810):

INFO:  System exits from STANDBY

NOTICE: BL2: v2.2-r2.0(release):

NOTICE: BL2: Built : 10:03:06, Apr 15 2021

INFO:  Using crypto library 'stm32_crypto_lib'

INFO:  BL2: Doing platform setup

INFO:  RAM: DDR3-DDR3L 16bits 533000Khz

INFO:  BL2 runs SP_MIN setup

INFO:  BL2: Skip loading image id 4

INFO:  BL2: Skip loading image id 5

NOTICE: BL2: Booting BL32

INFO:  Entry point address = 0x2ffeb000

INFO:  SPSR = 0x1d3

NOTICE: SP_MIN: v2.2-r2.0(release):

NOTICE: SP_MIN: Built : 10:03:09, Apr 15 2021

INFO:  ARM GICv2 driver initialized

INFO:  Set calibration timer to 60 sec

INFO:  ETZPC: UART1 (3) could be non secure

INFO:  ETZPC: SPI6 (4) could be non secure

INFO:  ETZPC: I2C6 (12) could be non secure

INFO:  SP_MIN: Initializing runtime services

INFO:  SP_MIN: Preparing exit to normal world <-- blocks here till watchdog kicks in and reset the board

Please suggest is this the issue with tfa or kernel ?

Thanks, Rishi

4 REPLIES 4
MBrei.4
Associate II

I have a similar problem, getting stuck after "SP_MIN: Preparing exit to normal world". Did you manage to solve the problem by yourself?

AKudr.1
Associate II

I have similar problem. If I use UART as wake up source (stop mode), then after putting character on a line I see power consumption increased and no output on board console.

If I use RTC for wake up (standby mode), then I see this:

INFO:  Reset reason (0x810):

INFO:  System exits from STANDBY

INFO:  Using SDMMC

INFO:   Instance 1

INFO:  Boot used partition fsbl1

NOTICE: BL2: v2.2-r1.0(debug):0e034c5

NOTICE: BL2: Built : 13:08:21, May 30 2021

INFO:  Using crypto library 'stm32_crypto_lib'

INFO:  BL2: Doing platform setup

INFO:  RAM: DDR3-1066/888 bin G 2x2Gb 533MHz v1.44

INFO:  BL2 runs SP_MIN setup

INFO:  BL2: Loading image id 4

INFO:  Loading image id=4 at address 0x2ffed000

INFO:  Image id=4 loaded: 0x2ffed000 - 0x2ffff000

INFO:  BL2: Skip loading image id 5

NOTICE: BL2: Booting BL32

INFO:  Entry point address = 0x2ffed000

INFO:  SPSR = 0x1d3

NOTICE: SP_MIN: v2.2-r1.0(debug):0e034c5

NOTICE: SP_MIN: Built : 13:08:21, May 30 2021

INFO:  ARM GICv2 driver initialized

INFO:  stm32mp IWDG1 (12): Secure

INFO:  ETZPC: CRYP1 (9) could be non secure

INFO:  SP_MIN: Initializing runtime services

INFO:  SP_MIN: Preparing exit to normal world

ERROR: Illegal access to 0xe0000000 in :

ERROR:     Non-Secure

ERROR:     Privilege

ERROR:     Read

After WDT restarts MPU.

Need help! Where is the issue? tf-a, kernel, u-boot???

AKudr.1
Associate II

I think that topicstarter as me uses own hardware implementation with stm32mp15x MPU. I have tested sleep/wakes on development board - it works. That is why I think that our problems in dts file definition of hardware resources that we changed opposite devboard shematic. For example, I removed type-c controller and make usb2 ehci host, set uart5 as console etc. But how it all could manage non privileged memory access while booting from standby?

AKudr.1
Associate II

Hello everyone!

I found that my device based on STM32MP157 not wakes up when I assign USB2 port to EHCI/OHCI controllers instead OTG in .dts file. When I use OTG in HOSTonly mode (I remove any USB TYPE-C controllers from I2C node in .dts also) it works fine and can sleep and wakes. Maybe it will be useful information for anybody. Good luck!