i.MX8M Mini EVK Android 11 Error

[territao]

Hello,

I downloaded Android 11 demo images to the i.MX8MMini EVK board via uuu, the first time everything works fine and the EVK can successfully load Android 11. The second time I download the same demo images, the LCD continuously shows the Android boot splash screen and outputs the below error messages.

Is there anything wrong with the uuu download process? What does the error message shown below mean?

[   70.795774] DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

[   70.796054] DEBUG: Build fingerprint: 'Android/evk_8mm/evk_8mm:11/RQ2A.210505.002/eng.bpendl.20220407.133922:userdebug/dev-keys'

[   70.804007] DEBUG: Revision: '0'

[   70.815769] DEBUG: ABI: 'arm64'

[   70.819343] DEBUG: Timestamp: 1970-01-01 00:01:18+0000

[   70.822616] DEBUG: pid: 580, tid: 580, name: credstore  >>> /system/bin/credstore <<<

[   70.827859] DEBUG: uid: 1076

[   70.835954] DEBUG: signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------

[   70.839041] DEBUG: Abort message: 'Check failed: chdir(data_dir.c_str()) != -1 chdir: /data/misc/credstore: No such file or directory'

[   70.846413] DEBUG:     x0  0000000000000000  x1  0000000000000244  x2  0000000000000006  x3  0000ffffd4b6b050

[   70.858665] DEBUG:     x4  0000000000000000  x5  0000000000000000  x6  0000000000000000  x7  7f7f7f7f7f7f7f7f

[   70.868935] DEBUG:     x8  00000000000000f0  x9  0000ed02ce5367e0  x10 ffffff80ffffffdf  x11 0000000000000001

[   70.878984] DEBUG:     x12 0000000000000000  x13 00000000000000df  x14 0000000000000010  x15 0000000000000000

[   70.889323] DEBUG:     x16 0000ed02ce5cfc80  x17 0000ed02ce5b13c0  x18 0000ed02cf30e000  x19 00000000000000ac

[   70.899434] DEBUG:     x20 0000000000000244  x21 00000000000000b2  x22 0000000000000244  x23 00000000ffffffff

[   70.909560] DEBUG:     x24 0000000000000000  x25 0000000000000000  x26 0000000000000000  x27 0000000000000000

[   70.919629] DEBUG:     x28 0000000000000000  x29 0000ffffd4b6b0d0

[   70.929708] DEBUG:     lr  0000ed02ce564544  sp  0000ffffd4b6b030  pc  0000ed02ce564574  pst 0000000000000000

[   70.943042] DEBUG:

[   70.955134] DEBUG: backtrace:

[   70.955407] DEBUG:       #00 pc 000000000004e574  /apex/com.android.runtime/lib64/bionic/libc.so (abort+180) (BuildId: 2338ca8a340db969666f0073f3371d96)

[   70.958647] DEBUG:       #01 pc 0000000000011e6c  /system/lib64/libbase.so (android::base::DefaultAborter(char const*)+12) (BuildId: 68451a7f9cd9977a087be310599bc932)

[   70.972590] DEBUG:       #02 pc 0000000000013ab0  /system/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_3::__invoke(char const*)+80) (BuildId: 68451a7f9cd9977a087be310599bc932)

[   70.987703] DEBUG:       #03 pc 0000000000013090  /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+320) (BuildId: 68451a7f9cd9977a087be310599bc932)

[   71.007374] DEBUG:       #04 pc 000000000000e3e4  /system/bin/credstore (main+924) (BuildId: a2970c6dc5aaea97c7676a0e6ddb432e)

[   71.022385] DEBUG:       #05 pc 0000000000049a34  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: 2338ca8a340db969666f0073f3371d96)

[   75.664963] init: starting service 'tombstoned'...

[   75.670339] init: Created socket '/dev/socket/tombstoned_crash', mode 666, user 1000, group 1000

[   75.679708] init: Created socket '/dev/socket/tombstoned_intercept', mode 666, user 1000, group 1000

[   75.689276] init: Created socket '/dev/socket/tombstoned_java_trace', mode 666, user 1000, group 1000

[   75.716721] init: Service 'tombstoned' (pid 591) exited with status 1

[   75.723240] init: Sending signal 9 to service 'tombstoned' (pid 591) process group...

[   75.731432] libprocessgroup: Successfully killed process cgroup uid 1058 pid 591 in 0ms

[   75.739802] init: updatable process 'tombstoned' exited 4 times before boot completed

[   75.749208] init: processing action (sys.init.updatable_crashing=1) from (/system/etc/init/flags_health_check.rc:10)

[   75.760261] init: starting service 'exec 32 (/system/bin/flags_health_check UPDATABLE_CRASHING)'...

Thanks,

Terri

[blairpendleton]

1. download android-11.0.0_2.2.0_image_8mmevk prebuilt files
2. execute uuu_imx_android_flash.sh script produce uuu.lst file (evk w/mipi-panel)
3. set evk switches for serial download
4. run uuu uuu.lst
5. set evk switches for mmc boot

[blairpendleton]

On boot, the mipi-panel shows the android boot animation screen indefinitely.  The serial console shows android init error (/system/bin/credstore) repeatedly.

If we flash older android_o8.1.0_1.5.1_8mm-beta_image_8mmevk prebuilt files, android boots correctly. And flashing android-11.0.0_2.2.0_image_8mmevk prebuilt files when android_o8 files have been installed, android-11 also boots correctly.   But this only works once.  Reflashing the same android-11.0.0_2.2.0_image_8mmevk prebuilt files a second time results in the repeated android init error and boot animation screen forever.

[blairpendleton]

Update: the /system/bin/credstore error due to missing /data/misc/credstore directory is a symptom of failing to mount /dev/block/dm-8 on /data.   When the system boots correctly, /dev/block/dm-1 thru dm-8 exist.   When the system fails to boot completely, /dev/block/dm-5 thru dm-8 are missing.   This behavior occurs when using u-boot-imx8mm.imx. 

We discovered that if we use trusty bootloader u-boot-imx8mm-trusty.imx, /dev/block/dm-1 thru dm-8 always exist after flashing and this problem does not occur.  My understanding is the trusty bootloader is not required, but we have decided to start using it for now as a workaround for this issue.

Any insight as to why the u-boot-imx8mm.imx bootloader fails would be appreciated.

[Zhiming_Liu]

How do you flash images?

Can you reflash again?