topic Re: iMX8qxpc0mek Android15 Automotive facing issue while flashing in i.MX Processors

iMX8qxpc0mek Android15 Automotive facing issue while flashing

Ram2 — Fri, 02 Jan 2026 08:48:59 GMT

Hi NXP Team,

We are trying to use Android15 Automotive bring up in iMX8qxpC0mek

Since its custom board , not an EVK

================ Boot logs============

U-Boot SPL 2025.04-g1fb4ea4fd9e4-dirty (Jan 02 2026 - 12:31:04 +0530)
Normal Boot
Trying to boot from MMC1
MMC: block number 0x4000 exceeds max(0x2000)
Failed to read rpmbkeyblob.Authentication key not yet programmed
Booting from bootloader_a...
UU
boot args 0x*** 0x*** 0x*** 0x0
SCFW: 00000***
SECO-FW: 00000***
initializing trusty (Project: imx8qxp, Build: nxa16252@lsv05559.swis.nl-cdc01.nxp.com-1, Built: 13:48:55 Aug 12 2025)
hwsecure: 22: hwsecure init.
INFO: trusty/user/app/secretkeeper/lib.rs:258 Secretkeeper TA startup, on: 'com.android.trusty.secretkeeper.authgraph', 'com.android.trusty.secretkeeper', 'com.android.trusty.secretkeeper.bootloader'
Core: 248 devices, 27 uclasses, devicetree: separate
Warning: Device tree includes old 'u-boot,dm-' tags: please fix by 2023.07!
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... Reading from MMC(0)... *** Warning - bad CRC, using default environment

[*]-Video Link 0dc0_power_domain [32] not owned by curr partition
sc_pm_set_resource_power_mode: resource:32 mode:3: res:4
Error: dc0_power_domain Power up failed! (error = -13)
probe video device failed, ret -5

[0] dpu@56180000, video
[1] lvds-channel@0, display
[2] panel, panel
In: serial
Out: serial
Err: serial

BuildInfo:
- SCFW 654907b6, SECO-FW c9de51c0, IMX-MKIMAGE 4c2e5b25, ATF automot
- U-Boot 2025.04-g1fb4ea4fd9e4-dirty

flash target is MMC:0
Net: No ethernet found.
INFO Initializing Trusty device
INFO selected trusty api version: 3 (requested 3)
INFO Initializing Trusty IPC device
INFO Initializing Trusty Hardware Crypto client
INFO Initializing RPMB storage proxy service
Authentication key not yet programmed
rpmb_proxy.c:279: ERROR proxy_handle_rpmb: rpmb_storage_send failed: 7
Authentication key not yet programmed
rpmb_proxy.c:279: ERROR proxy_handle_rpmb: rpmb_storage_send failed: 7
Authentication key not yet programmed
rpmb_proxy.c:279: ERROR proxy_handle_rpmb: rpmb_storage_send failed: 7
failed to read rpmb write counter
Authentication key not yet programmed
rpmb_proxy.c:279: ERROR proxy_handle_rpmb: rpmb_storage_send failed: 7
ss: init_rpmb_fs: bad static rpmb size, 2048
ss: storage_service_init: block_device_tipc_init failed (-1)
Authentication key not yet programmed
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
Verifying slot _a ...
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
fsl_validate_vbmeta_public_key_rpmb: Read public key error
avb_slot_verify.c:902: ERROR: vbmeta_a: Public key used to sign data rejected.
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
fsl_read_rollback_index_rpmb: read rollback from Trusty error!
Authentication key not yet programmed
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
fsl_read_rollback_index_rpmb: read rollback from Trusty error!
Authentication key not yet programmed
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
fsl_read_rollback_index_rpmb: read rollback from Trusty error!
Authentication key not yet programmed
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
verify FAIL, state: UNLOCK
boot 'boot_a' still
Kernel load addr 0x80280000 size 38883 KiB
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
ERROR - failed to read public key for keymaster
keymaster.c:318: ERROR Keymaster TIPC client not initialized!
keymaster.c:684: ERROR Keymaster TIPC client not initialized!
boota: set boot patch level failed.
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
secretkeeper.c:58: ERROR send_header_only_request: SecretKeeper client not initialized
secretkeeper.c:121: ERROR In secretkeeper_get_identity: failed (-1) to send request to Secretkeeper.
secretkeeper.c:150: ERROR Failed to get secretkeeper key (err = -1)!
kernel @ 80280000 (40566784)
ramdisk @ fc000000 (23203478)
fdt @ 82ab0400 (145053)
Moving Image from 0x80280000 to 0x80400000, end=0x82ab0000
## Flattened Device Tree blob at 82ab0400
Booting using the fdt blob at 0x82ab0400
Working FDT set to 82ab0400
Using Device Tree in place at 0000000082ab0400, end 0000000082ad6a9c
Working FDT set to 82ab0400
/bus@59000000/dma-controller@591f0000, 41740
/bus@59000000/dma-controller@599f0000, 42872
/bus@5a000000/dma-controller@5a1f0000, 62280
/bus@5a000000/dma-controller@5a1f0000, 62280
/bus@5a000000/dma-controller@5a9f0000, 62784
dc0_power_domain [32] not owned by curr partition
sc_pm_set_resource_power_mode: resource:32 mode:3: res:4
Error: dc0_power_domain Power up failed! (error = -13)
probe video device failed, ret -5
Authentication key not yet programmed

Starting kernel ...

Re: iMX8qxpc0mek Android15 Automotive facing issue while flashing

Ram2 — Fri, 02 Jan 2026 08:49:34 GMT

Facing above issue while flashing , can help what could be the issue

Re: iMX8qxpc0mek Android15 Automotive facing issue while flashing

Zhiming_Liu — Mon, 05 Jan 2026 02:18:46 GMT

Hi @Ram2

If you are using custom board, did you modify the source code referring the difference?

Here is bootlog on MEK board with flash command: .\uuu_imx_android_flash.bat -f imx8qxp -e -u c0

U-Boot SPL 2025.04-g6bf602d3b5ab (Sep 16 2025 - 19:00:07 +0200) Normal Boot Trying to boot from MMC1 Magic is incorrect. Error validating A/B metadata from disk. Resetting and writing new A/B metadata to disk. Authentication key not yet programmed Booting from bootloader_a... UU boot args 0x*** 0x*** 0x*** 0x0 SCFW: 00000*** SECO-FW: 00000*** initializing trusty (Project: imx8qxp, Build: nxa16252@lsv05559.swis.nl-cdc01.nxp.com-1, Built: 13:48:55 Aug 12 2025) hwsecure: 22: hwsecure init. INFO: trusty/user/app/secretkeeper/lib.rs:258 Secretkeeper TA startup, on: 'com.android.trusty.secretkeeper.authgraph', 'com.android.trusty.secretkeeper', 'com.android.trusty.secretkeeper.bootloader' Core: 262 devices, 31 uclasses, devicetree: separate MMC: FSL_SDHC: 0, FSL_SDHC: 1 Loading Environment from MMC... Reading from MMC(0)... *** Warning - bad CRC, using default environment [*]-Video Link 0dc0_power_domain [32] not owned by curr partition sc_pm_set_resource_power_mode: resource:32 mode:3: res:4 Error: dc0_power_domain Power up failed! (error = -13) probe video device failed, ret -5 [0] dpu@56180000, video [1] lvds-channel@0, display In: serial Out: serial Err: serial BuildInfo: - SCFW 654907b6, SECO-FW c9de51c0, IMX-MKIMAGE 4c2e5b25, ATF automot - U-Boot 2025.04-g6bf602d3b5ab flash target is MMC:0 Net: eth0: ethernet@5b040000 [PRIME]Could not get PHY for FEC1: addr 1 INFO Initializing Trusty device INFO selected trusty api version: 3 (requested 3) INFO Initializing Trusty IPC device INFO Initializing Trusty Hardware Crypto client INFO Initializing RPMB storage proxy service Authentication key not yet programmed rpmb_proxy.c:279: ERROR proxy_handle_rpmb: rpmb_storage_send failed: 7 Authentication key not yet programmed rpmb_proxy.c:279: ERROR proxy_handle_rpmb: rpmb_storage_send failed: 7 Authentication key not yet programmed rpmb_proxy.c:279: ERROR proxy_handle_rpmb: rpmb_storage_send failed: 7 failed to read rpmb write counter Authentication key not yet programmed rpmb_proxy.c:279: ERROR proxy_handle_rpmb: rpmb_storage_send failed: 7 ss: init_rpmb_fs: bad static rpmb size, 2048 ss: storage_service_init: block_device_tipc_init failed (-1) Authentication key not yet programmed Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized Verifying slot _a ... avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized fsl_validate_vbmeta_public_key_rpmb: Read public key error avb_slot_verify.c:902: ERROR: vbmeta_a: Public key used to sign data rejected. avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized fsl_read_rollback_index_rpmb: read rollback from Trusty error! Authentication key not yet programmed avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized fsl_read_rollback_index_rpmb: read rollback from Trusty error! Authentication key not yet programmed avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized fsl_read_rollback_index_rpmb: read rollback from Trusty error! Authentication key not yet programmed avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized verify FAIL, state: UNLOCK boot 'boot_a' still Kernel load addr 0x80280000 size 38883 KiB avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized ERROR - failed to read public key for keymaster keymaster.c:318: ERROR Keymaster TIPC client not initialized! keymaster.c:684: ERROR Keymaster TIPC client not initialized! boota: set boot patch level failed. avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized secretkeeper.c:58: ERROR send_header_only_request: SecretKeeper client not initialized secretkeeper.c:121: ERROR In secretkeeper_get_identity: failed (-1) to send request to Secretkeeper. secretkeeper.c:150: ERROR Failed to get secretkeeper key (err = -1)! kernel @ 80280000 (40566784) ramdisk @ fc000000 (23201967) fdt @ 82ab0400 (129950) Moving Image from 0x80280000 to 0x80400000, end=0x82ab0000 ## Flattened Device Tree blob at 82ab0400 Booting using the fdt blob at 0x82ab0400 Working FDT set to 82ab0400 Using Device Tree in place at 0000000082ab0400, end 0000000082ad2f9d Working FDT set to 82ab0400 /bus@59000000/dma-controller@591f0000, 36432 /bus@59000000/dma-controller@599f0000, 37564 /bus@5a000000/dma-controller@5a1f0000, 54600 /bus@5a000000/dma-controller@5a1f0000, 54600 /bus@5a000000/dma-controller@5a9f0000, 55104 dc0_power_domain [32] not owned by curr partition sc_pm_set_resource_power_mode: resource:32 mode:3: res:4 Error: dc0_power_domain Power up failed! (error = -13) probe video device failed, ret -5 Authentication key not yet programmed Starting kernel ... [ 0.000000][ T0] Booting Linux on physical CPU 0x0000000000 [0x410fd042] [ 0.000000][ T0] Linux version 6.12.23-android16-5-maybe-dirty-4k (kleaf@build-host) (Android (12833971, +pgo, +bolt, +lto, +mlgo, based on r536225) clang version 19.0.1 (https://android.googlesource.com/toolchain/llvm-project b3a530ec6537146650e42be89f1089e9a3588460), LLD 19.0.1) #1 SMP PREEMPT Thu Jan 1 00:00:00 UTC 1970 [ 0.000000][ T0] KASLR enabled [ 0.000000][ T0] Machine model: Freescale i.MX8QXP MEK [ 0.000000][ T0] Malformed early option 'earlycon' [ 0.000000][ T0] Enabling dynamic shadow call stack [ 0.000000][ T0] efi: UEFI not found.

Best Regards,
Zhiming

Re: iMX8qxpc0mek Android15 Automotive facing issue while flashing

Ram2 — Mon, 05 Jan 2026 05:50:00 GMT

Hi @Zhiming_Liu

We are using same flashing command

sudo ./uuu_imx_android_flash.sh -f imx8qxp -a -u c0 -e -c0

Still I see below error

hwcrypto.c:94: ERROR hwcrypto_do_tipc: HWCRYPTO TIPC client not initialized
Kernel load addr 0x80280000 size 38883 KiB
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
ERROR - failed to read public key for keymaster
keymaster.c:318: ERROR Keymaster TIPC client not initialized!
keymaster.c:684: ERROR Keymaster TIPC client not initialized!
boota: set boot patch level failed.
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
secretkeeper.c:58: ERROR send_header_only_request: SecretKeeper client not initialized
secretkeeper.c:121: ERROR In secretkeeper_get_identity: failed (-1) to send request to Secretkeeper.
secretkeeper.c:150: ERROR Failed to get secretkeeper key (err = -1)!
kernel @ 80280000 (40566784)
ramdisk @ fc000000 (23203479)
fdt @ 82ab0400 (145053)
Moving Image from 0x80280000 to 0x80400000, end=0x82ab0000
## Flattened Device Tree blob at 82ab0400
Booting using the fdt blob at 0x82ab0400
Working FDT set to 82ab0400
Using Device Tree in place at 0000000082ab0400, end 0000000082ad6a9c
Working FDT set to 82ab0400
hwcrypto.c:94: ERROR hwcrypto_do_tipc: HWCRYPTO TIPC client not initialized
/bus@59000000/dma-controller@591f0000, 41740
/bus@59000000/dma-controller@599f0000, 42872
/bus@5a000000/dma-controller@5a1f0000, 62280
/bus@5a000000/dma-controller@5a1f0000, 62280
/bus@5a000000/dma-controller@5a9f0000, 62784
hwcrypto.c:94: ERROR hwcrypto_do_tipc: HWCRYPTO TIPC client not initialized
dc0_power_domain [32] not owned by curr partition
sc_pm_set_resource_power_mode: resource:32 mode:3: res:4
Error: dc0_power_domain Power up failed! (error = -13)
probe video device failed, ret -5
hwcrypto.c:94: ERROR hwcrypto_do_tipc: HWCRYPTO TIPC client not initialized
Authentication key not yet programmed

Starting kernel ...

U-Boot SPL 2025.04-g1fb4ea4fd9e4-dirty (Jan 03 2026 - 12:58:24 +0530)
Normal Boot
Trying to boot from MMC1
MMC: block number 0x4000 exceeds max(0x2000)
Failed to read rpmbkeyblob.Authentication key not yet programmed
Load or verify bootloader_b fail, setting unbootable..
No bootable slots found, try to boot into recovery mode...
Authentication key not yet programmed
Error: -38
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

We have done pin muxing changes w.r.t to custom board

Re: iMX8qxpc0mek Android15 Automotive facing issue while flashing

Zhiming_Liu — Tue, 06 Jan 2026 01:41:23 GMT

Hi @Ram2

Did you finish the DDR calibration?

Best Regards,
Zhiming

Re: iMX8qxpc0mek Android15 Automotive facing issue while flashing

Ram2 — Tue, 06 Jan 2026 05:03:55 GMT

Hi @Zhiming_Liu

We didnt finish the DDR calibration , Can you please help with steps for DDR calibration

Is there any generic steps or tool is required

Re: iMX8qxpc0mek Android15 Automotive facing issue while flashing

Zhiming_Liu — Tue, 06 Jan 2026 06:25:26 GMT

Hi @Ram2
Please refer this knowledge base. Need to get new timing.c from tool and then replace it in uboot.

i.MX 8/8X Family DDR Tools Release

Best Regards,
Zhiming