cancel
Showing results for 
Search instead for 
Did you mean: 

stm32mp15x emmc reboot stuck-up

MWoło.2
Senior II

Hi,

I have a problem with hanging up my board occasionally when an issue from the console reboot.

I read about and the internet says this is a problem with the EMMC memory's power cycle.

So I followed by a link

https://github.com/orangepi-xunlong/openwrt/commit/14d3a99e17f2ec6097eeef97530cba2d62c58d3c#diff-1335d7b270cc58c5342d5e2843730580bfe5d8048d765abb753050095929d85d

but still, after a few reboots my board stacked.

My final message from the console is as follows

 

[  OK  ] Stopped Create Static Device Nodes in /dev.                            
[  OK  ] Reached target System Shutdown.                                        
[  OK  ] Reached target Late Shutdown Services.                                 
[  OK  ] Finished System Reboot.                                                
[  OK  ] Reached target System Reboot.                                          
[   32.494373] watchdog: watchdog0: watchdog did not stop!                      
[   32.522678] systemd-shutdown[1]: Using hardware watchdog 'STM32 Independent 0
[   32.533457] systemd-shutdown[1]: Watchdog running with a timeout of 2min.    
[   32.559399] systemd-shutdown[1]: Syncing filesystems and block devices.      
[   32.687090] systemd-shutdown[1]: Sending SIGTERM to remaining processes...   
[   32.713669] systemd-journald[685]: Received SIGTERM from PID 1 (systemd-shut.
[   32.738780] systemd-shutdown[1]: Sending SIGKILL to remaining processes...   
[   32.764536] systemd-shutdown[1]: Unmounting file systems.                    
[   32.774792] [1459]: Remounting '/' read-only with options 'n/a'.             
[   32.798594] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null). Quota mode: disab.
[   32.825938] systemd-shutdown[1]: All filesystems unmounted.                  
[   32.830174] systemd-shutdown[1]: Deactivating swaps.                         
[   32.835585] systemd-shutdown[1]: All swaps deactivated.                      
[   32.840200] systemd-shutdown[1]: Detaching loop devices.                     
[   32.854929] systemd-shutdown[1]: All loop devices detached.                  
[   32.859153] systemd-shutdown[1]: Stopping MD devices.                        
[   32.865032] systemd-shutdown[1]: All MD devices stopped.                     
[   32.869346] systemd-shutdown[1]: Detaching DM devices.                       
[   32.875192] systemd-shutdown[1]: All DM devices detached.                    
[   32.879905] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD de.
[   32.924796] systemd-shutdown[1]: Syncing filesystems and block devices.      
[   32.930334] systemd-shutdown[1]: Rebooting.                                  
[   33.167515] reboot: Restarting system                                        
INFO:    PSCI Power Domain Map:                                                 
INFO:      Domain Node : Level 1, parent_node -1, State ON (0x0)                
INFO:      Domain Node : Level 0, parent_node 0, State ON (0x0)                 
INFO:      CPU Node : MPID 0x0, parent_node 0, State ON (0x0)                   
INFO:      CPU Node : MPID 0x1, parent_node 0, State ON (0x0)  

 

How to resolve this issue?

Thanks

BR

Michał

1 ACCEPTED SOLUTION

Accepted Solutions
PatrickF
ST Employee

Hi @MWoło.2 

this might come up from a know limitation, not linked to eMMC.

In case your board did not use STPMIC1 for supply (which issue a power cycle on VDDCORE in case of reset), you should connect NRST to NRST_CORE with a 1nF capacitor as listed in ES0438 "Incorrect reset of glitch-free kernel clock switch" or AN5031 "Discrete supplies example 3.3 V I/Os with DDR3L"

Regards,

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

View solution in original post

2 REPLIES 2
PatrickF
ST Employee

Hi @MWoło.2 

this might come up from a know limitation, not linked to eMMC.

In case your board did not use STPMIC1 for supply (which issue a power cycle on VDDCORE in case of reset), you should connect NRST to NRST_CORE with a 1nF capacitor as listed in ES0438 "Incorrect reset of glitch-free kernel clock switch" or AN5031 "Discrete supplies example 3.3 V I/Os with DDR3L"

Regards,

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
MWoło.2
Senior II

Hi Patrick,

it's working. I take care of everything else without connecting through the cap that two mentioned NRST.

Thanks a lot, the topic can be closed.

Best Regards

Michał