Getting "Synchronous Abort" handler error in IMX8QM

[vinothkumars]

Hi All,

I got following error and I unable to find out the address (00000000789f0000) from .map file.

U-Boot SPL 2018.03-00003-g0d0fb52-dirty (Aug 20 2021 - 18:19:27 +0530)
Trying to boot from MMC1
Authentication key not yet programmed
keyslot package magic error, do nothing here!
Authentication key not yet programmed
Booting from bootloader_a...U
welcome to lk/MP

boot args 0x2000000 0xfe000000 0x2000 0x0
generic_arm64_map_regs: failed -5 name=gic
initializing trusty (Built: 17:00:46 Mar 5 2019)
Initializing Trusted OS SMC handler
int rebuild_hset_all(struct uctx *):238: Rebuilding all handles set
hwcrypto: 222: Initializing
hwrng_caam: 44: Init HWRNG service provider
hwrng_srv: 256: Start HWRNG service
int rebuild_hset_all(struct uctx *):238: Rebuilding all handles set
hwcrypto_caam: 78: Init HWCRYPTO service provider
hwcrypto_srv: 306: Start HWCRYPTO service
hwkey_caam: 169: Init HWKEY service provider
hwkey_caam: 138: Invalid magic
hwkey_srv: 331: Start HWKEY service
hwcrypto: 237: enter main event loop
int rebuild_hset_all(struct uctx *):238: Rebuilding all handles set
int rebuild_hset_all(struct uctx *):238: Rebuilding all handles set
int rebuild_hset_all(struct uctx *):238: Rebuilding all handles set
MMC: FSL_SDHC: 0
In: serial@5a060000
Out: serial@5a060000
Err: serial@5a060000
flash target is MMC:0
libtipc.c: INFO Initializing Trusty device
trusty_dev.c: INFO selected trusty api version: 3 (requested 3)
libtipc.c: INFO Initializing Trusty IPC device
libtipc.c: INFO Initializing RPMB storage proxy service
ss: get_rpmb_auth_key: failed to get key: -2
ss: proxy_connect: can't get storage auth key: (-2)
ipc: do_connect: failure initializing channel state (1001)
rpmb_proxy.c:312: ERROR rpmb_storage_proxy_init: unexpected proxy channel close
libtipc.c:93: ERROR Initlializing RPMB storage proxy service failed (-8)
Authentication key not yet programmed
libtipc.c: INFO Initializing Trusty Hardware Crypto client
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_vbmeta_image.c:206: ERROR: Hash does not match!
avb_slot_verify.c:692: ERROR: vbmeta_a: Error verifying vbmeta image: HASH_MISMATCH
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_slot_verify.c:388: ERROR: boot_a: Hash of data does not match digest in descriptor.
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 9010 KiB
kernel @ 80280000 (9225875)
ramdisk @ 83400000 (2588437)
fdt @ 83200000 (104058)
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!
avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized
ipc_dev.c:306: ERROR trusty_ipc_dev_close: secure OS returned (-7)
## Flattened Device Tree blob at 83200000
Booting using the fdt blob at 0x83200000
Using Device Tree in place at 0000000083200000, end 000000008321c679
/dma-controller@5a1f0000, 71520
/dma-controller@591F0000, 72312
/dma-controller@591F0000, 72312
/dma-controller@599F0000, 73288

Starting kernel ...

"Synchronous Abort" handler, esr 0x02000000
elr: 00000000789f0000 lr : 0000000080021b08 (reloc)
elr: 0000000081090000 lr : 00000000886c1b08
x0 : 0000000083200000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000080280000 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 000000008873c328 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 0000000083abdd8e
x14: 00000000843a8ea2 x15: 00000000886c1244
x16: 000000008227fff7 x17: 0000000000000000
x18: 0000000083abdd78 x19: 000000008873c170
x20: 0000000000000000 x21: 0000000083aae9b8
x22: 0000000000000003 x23: 0000000083aae9b8
x24: 0000000000000000 x25: 0000000000000000
x26: 0000000000000000 x27: 00000000886c1b14
x28: 0000000000000000 x29: 0000000083aae780

Resetting CPU ...

resetting ...

[igorpadykov]

Hi Vinothkumar

one can try to debug it using AN12631  AN12631: Normal and Secure Debug for i.MX8/8X Family of Applications Processors – Application Note

Best regards
igor

[vinothkumars]

Thank you Igor for the reply.

But, I unable to debug using this document.

Will you please give some more information what exactly happens here ?

[igorpadykov]

had board passed ddr test

https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-8-8X-Family-DDR-Tools-Release/ta-p/...

Best regards
igor

[vinothkumars]

Yes Igor

Please find the test report,

[vinothkumars]

Hi @igorpadykov ,

This error I observed after sometime from power off to power on and not in all time.

And also address are start from 0x80000000 but here the error appends from 

789f0000

[igorpadykov]

>This error I observed after sometime from power off to power on..

please check below requirement

 

Best regards
igor

[vinothkumars]

Thank you Igor for the reply.

Instead of power off the board I tried "shutdown" from command line and the device power off take sometime compare to normal on and off. but, still I faced same error.

And also I measure all voltage source all in 0 v only