Tool/software:
Prashant,
Follow previous w2e ticket
Customer use SDK: 09_01_00_08 , Kernel Version: 6.1.46-rt13 on their own board.
We use KIOXIA emmc sdhci0 boot, then do power on and off cycle test and found ATF error happen occasionally.
Customer suspend the investigation but recently got more fail cases and resume the debug.
Boot log will stop on ATF as below.
U-Boot SPL 2023.04-gd5e737886b (Dec 24 2024 - 03:25:05 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
SPL initial stack usage: 13384 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...
NOTICE: BL31: v2.9(rve.:.2-910-6d4ag175733-di2td
In the old discussion, two suspect points.
1. eMMC stability
2. DDR stability
From the log, previous discussion pointed there is no eMMC access and suspect more about DDR stability.
We had checked and verified customer DDR layout and setting and also done DDR test on u-boot and Linux kernel and exclude hardware design issue.
Now customer had tried to connect CCS when stuck and below contain the data print out in files.
Program Counter stop point on A53 is 0x9E788200.
Program Counter stop point on R5 is 0x2596.
May you provide clue on what could be the root cause?
Will it be possible the TIFS response stop?
A53:
R5F:
BR, Rich