IMX8MP Android Reboot got struck booting up

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IMX8MP Android Reboot got struck booting up

568 Views
VeeraH
Contributor I

We are coming across weird behaviour on Android booting from eMMC. Once the android gets booted and then we tried to reboot the system. Android boot got struck with following log and does not shows anything on the display.

[ 22.573053][ T1] init: starting service 'zygote'...
[ 22.579238][ T1] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[ 22.588322][ T1] init: Created socket '/dev/socket/usap_pool_primary', mode 660, user 0, group 100
[ 22.601409][ T1] init: starting service 'zygote_secondary'...
[ 22.608402][ T1] init: Created socket '/dev/socket/zygote_secondary', mode 660, user 0, group 1000
[ 22.618524][ T1] init: Created socket '/dev/socket/usap_pool_secondary', mode 660, user 0, group 0
[ 27.573820][ T1] init: starting service 'netd'...
[ 27.579556][ T1] init: Created socket '/dev/socket/dnsproxyd', mode 660, user 0, group 3003
[ 27.588737][ T1] init: Created socket '/dev/socket/mdns', mode 660, user 0, group 1000
[ 27.597642][ T1] init: Created socket '/dev/socket/fwmarkd', mode 660, user 0, group 3003
[ 27.610618][ T1] init: starting service 'zygote'...
[ 27.616618][ T1] init: Created socket '/dev/socket/zygote', mode 660, user 0, group 1000
[ 27.626067][ T1] init: Created socket '/dev/socket/usap_pool_primary', mode 660, user 0, group 100
[ 27.639383][ T1] init: starting service 'zygote_secondary'...
[ 27.646429][ T1] init: Created socket '/dev/socket/zygote_secondary', mode 660, user 0, group 1000
[ 27.656532][ T1] init: Created socket '/dev/socket/usap_pool_secondary', mode 660, user 0, group 0

But when we try to boot same Android image from Micro SD Card, we does not come across this issue.

Also when we configure usdhc3 (eMMC) max-frequency as 50 MHz, we does not come across this issue.

 

When USDHC3 max-frequency is 100 MHz, we are getting this issue around 3 out 10 times reboot.

When USDHC3 max-frequency is 200 MHz, we are getting this issue around 6 out 10 times reboot.

 

0 Kudos
5 Replies

495 Views
VeeraH
Contributor I

We validated the hardware individually, it works fine. Android BSP validated as below,

 

WiFi / Bluetooth => Works fine when we try to boot from SD Card

eMMC Boot => works fine without bt8xxx bluetooth driver, after adding it, reboot get struck on eMMC with 200 MHz, but with 50 MHz works fine.

0 Kudos

547 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

Are you running your test in an NXP EVK?
Also, please share the Android BSP version.

Saludos,
Aldo.

0 Kudos

529 Views
VeeraH
Contributor I

We are running it on our own custom hardware.

Android BSP version : imx-android-11.0.0_2.6.0/

0 Kudos

521 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

I would recommend to check the hardware first, since the issue happen at higher speed and rather randomly I would suggest to check with an oscilloscope and compare failing vs passing test.

Saludos,
Aldo.

0 Kudos

494 Views
VeeraH
Contributor I

We validated the hardware individually, it works fine. Android BSP validated as below,

WiFi / Bluetooth => Works fine when we try to boot from SD Card

eMMC Boot => eMMC boots fine with 200/100 MHz without bt8xxx bluetooth driver loaded. After adding bt8xxx driver, reboot get struck on eMMC with 200/100 MHz, but with 50 MHz works fine.

0 Kudos