AM623: Fixup A53 CPU Frequency by Speed Grade Problem

oguzhan mutlu

Part Number: AM623

Tool/software:

Hi,

We're trying to update our U-Boot version. There is a new update "fixup_a53_cpu_freq_by_speed_grade" function which changes A53 clock by checking speed grade of device.

We have "T" grade and "S" grade boards. T grade in 1.25Ghz works fine and boots as expected. With the same firmware the S grade one fails booting. Before this update there was no such function so both devices were booting with the same firmware. I'll put logs below.

What is the problem? Should we change something in ClkTree or RAM configurations to compatible with 1Ghz configuration. Or should we change something in ATF ?

U-Boot SPL 2025.04 (Jan 01 1970 - 01:00:00 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
Changed A53 CPU frequency to 1000000000Hz (S grade) in DT
SPL initial stack usage: 13424 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE: BL31: v2.1▒▒&+c+
▒+K▒▒L▒▒▒ihѝ BL31: Built : 01:00:00, Jan 1 1970
ERROR: Timeout waiting for thread SP_RESPONSE to fill
ERROR: Thread SP_RESPONSE verification failed (-60)
ERROR: Message receive failed (-60)
ERROR: Failed to get response (-60)
ERROR: Transfer send failed (-60)
ERROR: Timeout waiting for thread SP_RESPONSE to fill
ERROR: Thread SP_RESPONSE verification failed (-60)
ERROR: Message receive failed (-60)
ERROR: Failed to get response (-60)
ERROR: Transfer send failed (-60)
ERROR: Unable to query firmware capabilities (-60)
I/TC:
I/TC: OP-TEE version: 4.2.0 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Thu Jan 1 01:00:00 UTC 1970 aarch64
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 ti_sci_init:486 Unable to communicate with control firmware (-65523)
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000f1978 failed
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 tee_otp_get_hw_unique_key:97 Could not get HUK
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000f19a8 failed
I/TC: Activated SA2UL device
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 sa2ul_init:106 Could not change TRNG firewall owner
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000f19b0 failed
E/TC:0 0
E/TC:0 0 Core data-abort at address 0x14 (translation fault)
E/TC:0 0 esr 0x96000005 ttbr0 0x9e992000 ttbr1 0x00000000 cidr 0x0
E/TC:0 0 cpu #0 cpsr 0x800003c4
E/TC:0 0 x0 000000009e8f6000 x1 0000000000000000
E/TC:0 0 x2 0000000000000000 x3 0000000000000000
E/TC:0 0 x4 0000000000000050 x5 000000009e982d70
E/TC:0 0 x6 ffffffffffffffb0 x7 000000000007fd20
E/TC:0 0 x8 000000009e982f80 x9 000000009e903000
E/TC:0 0 x10 0000000000000008 x11 000000009e993f30
E/TC:0 0 x12 0000000000000000 x13 000000009e993ec0
E/TC:0 0 x14 0000000000000000 x15 0000000000000000
E/TC:0 0 x16 000000009e81d848 x17 0000000000000000
E/TC:0 0 x18 0000000000000000 x19 000000009e994200
E/TC:0 0 x20 000000009e994208 x21 000000009e8f6000
E/TC:0 0 x22 000000009e8f6000 x23 000000009e8f6ea0
E/TC:0 0 x24 000000009e8f5d60 x25 0000000000000000
E/TC:0 0 x26 0000000000000000 x27 0000000000000000
E/TC:0 0 x28 0000000000000000 x29 000000009e994170
E/TC:0 0 x30 000000009e8180f8 elr 000000009e818108
E/TC:0 0 sp_el0 000000009e994170
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0 0x9e818108
E/TC:0 0 0x9e808aec
E/TC:0 0 0x9e8232d8
E/TC:0 0 0x9e808cb0
E/TC:0 0 Panic 'unhandled pageable abort' at core/arch/arm/kernel/abort.c:582 <abort_handler>
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0 0x9e808f98
E/TC:0 0 0x9e81fcdc
E/TC:0 0 0x9e80787c
E/TC:0 0 0x9e804a5c

Thanks for helping,

Best Regards

4 months ago

0 Bin Liu 4 months ago

TI__Guru**** 169011 points

Hi, I am out of office for the next two weeks. Please expect delayed response.

0 Divyansh Mittal 4 months ago in reply to Bin Liu

TI__Expert 8720 points

Hi,
Can you please share your software setup?
From you logs, it seems you are getting this error with 9.01 SDK? and the patch you mentioned was released much later.
Are you backporting that patch to 9.01 SDK?

0 oguzhan mutlu 4 months ago in reply to Divyansh Mittal

Prodigy 60 points

Hi Dinyash,

We' re using mainline U-Boot version not TI SDK. Previous one was v2024.04. New update is v2025.04. We are patching our customization on top of it. I tried to comment out this "fixup_a53_cpu_freq_by_speed_grade" and it was working fine.

Here is my boot setup;

U-Boot Mainline - v2025.04 - 34820924edbc4ec7803eb89d9852f4b870fa760a

ATF Mainline - master - 00f1ec6b8740ccd403e641131e294aabacf2a48b

OPTEE Mainline - 4.2.0 - 12d7c4ee4642d2d761e39fbcf21a06fb77141dea

+1 Divyansh Mittal 4 months ago in reply to oguzhan mutlu

TI__Expert 8720 points

Hi,
Please apply the following patch and rebuild to see if it works:
https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/0002_2D00_arm_2D00_mach_2D00_k3_2D00_am62_2D00_Fixup_2D00_a53_2D00_max_2D00_cpu_2D00_frequency_2D00_by.patch

0 oguzhan mutlu 4 months ago in reply to Divyansh Mittal

Prodigy 60 points

Thank you Divyansh!

0 oguzhan mutlu 4 months ago in reply to Divyansh Mittal

Prodigy 60 points

Hi Again Divyansh,

I re-tested the patch but actually it seems this solution doesn't effect to our problem. I was using soft reset while testing and it was ok. But when I use hard reset (power off) the problem still exist.

I tried to test TI SDK's U-Boot versions like "ti-u-boot-2025.01" but problem also exist on these branches. I also tried to change clock directly from DTS file but the result is the same.

Any ideas?

Best Regards,

0 Divyansh Mittal 3 months ago in reply to oguzhan mutlu

TI__Expert 8720 points

Hi,
We are trying to replicate your issue on our side. Please expect a response by the end of this week.

0 Divyansh Mittal 3 months ago in reply to Divyansh Mittal

TI__Expert 8720 points

Hi,
By that time, can you please add debug prints in the patches and share results. (especially index, size, rates, k3_get_a53_max_frequency(), k3_get_speed_grade(), max_freq)
Is there any difference in bootlogs when you see the error in soft vs hard reset?

0 oguzhan mutlu 3 months ago in reply to Divyansh Mittal

Prodigy 60 points

Hi,

I'll provide logs. In my opinion the difference between soft and hard reset is connecting to TI's security core. Before soft reset I was using previous working version for updating bootloader (2024.04). So the core connection was already done and when soft reset the connection isn't lost. But when I do hard reset, the connection lost and never recover again.

0 Divyansh Mittal 3 months ago in reply to oguzhan mutlu

TI__Expert 8720 points

Hi,
We are still awaiting your bootlogs for hard vs warm reset. Please share when you have those.

0 oguzhan mutlu 3 months ago in reply to Divyansh Mittal

Prodigy 60 points

This is HARD RESET;

=>
U-Boot SPL 2025.04-00001-g102850fa9837-dirty (Jun 04 2025 - 15:11:53 +0300)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
**************** rates 13277755, index 1, size 8
Changed A53 CPU frequency to 1000000000Hz (S grade) in DT
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...
K��L�ڵihѝ BL31: Built : 01:00:00, Jan 1 1970
ERROR: Timeout waiting for thread SP_RESPONSE to fill
ERROR: Thread SP_RESPONSE verification failed (-60)
ERROR: Message receive failed (-60)
ERROR: Failed to get response (-60)
ERROR: Transfer send failed (-60)
ERROR: Timeout waiting for thread SP_RESPONSE to fill
ERROR: Thread SP_RESPONSE verification failed (-60)
ERROR: Message receive failed (-60)
ERROR: Failed to get response (-60)
ERROR: Transfer send failed (-60)
ERROR: Unable to query firmware capabilities (-60)
I/TC:
I/TC: OP-TEE version: 4.2.0 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Thu Jan 1 01:00:00 UTC 1970 aarch64
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 ti_sci_init:486 Unable to communicate with control firmware (-65523)
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000f1978 failed
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 tee_otp_get_hw_unique_key:97 Could not get HUK
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000f19a8 failed
I/TC: Activated SA2UL device
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 sa2ul_init:106 Could not change TRNG firewall owner
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000f19b0 failed
E/TC:0 0
E/TC:0 0 Core data-abort at address 0x14 (translation fault)
E/TC:0 0 esr 0x96000005 ttbr0 0x9e992000 ttbr1 0x00000000 cidr 0x0
E/TC:0 0 cpu #0 cpsr 0x800003c4
E/TC:0 0 x0 000000009e8f6000 x1 0000000000000000
E/TC:0 0 x2 0000000000000000 x3 0000000000000000
E/TC:0 0 x4 0000000000000050 x5 000000009e982d70
E/TC:0 0 x6 ffffffffffffffb0 x7 000000000007fd20
E/TC:0 0 x8 000000009e982f80 x9 000000009e903000
E/TC:0 0 x10 0000000000000008 x11 000000009e993f30
E/TC:0 0 x12 0000000000000000 x13 000000009e993ec0
E/TC:0 0 x14 0000000000000000 x15 0000000000000000
E/TC:0 0 x16 000000009e81d848 x17 0000000000000000
E/TC:0 0 x18 0000000000000000 x19 000000009e994200
E/TC:0 0 x20 000000009e994208 x21 000000009e8f6000
E/TC:0 0 x22 000000009e8f6000 x23 000000009e8f6ea0
E/TC:0 0 x24 000000009e8f5d60 x25 0000000000000000
E/TC:0 0 x26 0000000000000000 x27 0000000000000000
E/TC:0 0 x28 0000000000000000 x29 000000009e994170
E/TC:0 0 x30 000000009e8180f8 elr 000000009e818108
E/TC:0 0 sp_el0 000000009e994170
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0 0x9e818108
E/TC:0 0 0x9e808aec
E/TC:0 0 0x9e8232d8
E/TC:0 0 0x9e808cb0
E/TC:0 0 Panic 'unhandled pageable abort' at core/arch/arm/kernel/abort.c:582 <abort_handler>
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0 0x9e808f98
E/TC:0 0 0x9e81fcdc
E/TC:0 0 0x9e80787c
E/TC:0 0 0x9e804a5c

This is SOFT RESET;

U-Boot 2024.04-IID-CRA-ETHBOOT (Jan 01 1970 - 01:00:00 +0000)

SoC: AM62X SR1.0 HS-FS
Model: Siemens SIMATIC RF680V2
DRAM: 2 GiB
***********************************************************
Development Device
***********************************************************
Core: 42 devices, 22 uclasses, devicetree: separate
MMC: mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In: serial@2850000
Out: serial@2850000
Err: serial@2850000
Net: eth0: ethernet@8000000port@1
Hit any key to stop autoboot: 0
=> mmc erase 0x2000 0x4600

MMC erase: dev # 0, block # 8192, count 17920 ... 17920 blocks erased: OK
=> dhcp flash.bin
link up on port 1, speed 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.45.207 (2 ms)
Using ethernet@8000000port@1 device
TFTP from server 192.168.45.199; our IP address is 192.168.45.207
Filename 'flash.bin'.
Load address: 0x82000000
Loading: ################################################## 8.8 MiB
5.8 MiB/s
done
Bytes transferred = 9175040 (8c0000 hex)
=> mmc write ${loadaddr} 0x2000 0x4600

MMC write: dev # 0, block # 8192, count 17920 ... 17920 blocks written: OK
=> reset
resetting ...

U-Boot SPL 2025.04-00001-g102850fa9837-dirty (Jun 04 2025 - 15:11:53 +0300)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
**************** rates 13277755, index 1, size 8
Changed A53 CPU frequency to 1000000000Hz (S grade) in DT
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE: BL31: v2.�K̔release):
NOTICE: BL31: Built : 01:00:00, Jan 1 1970
I/TC:
I/TC: OP-TEE version: 4.2.0 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Thu Jan 1 01:00:00 UTC 1970 aarch64
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2025.04-00001-g102850fa9837-dirty (Jun 04 2025 - 15:12:24 +0300)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
SPL initial stack usage: 1808 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed

U-Boot 2025.04-00001-g102850fa9837-dirty (Jun 04 2025 - 15:12:24 +0300)

SoC: AM62X SR1.0 HS-FS
Model: Siemens SIMATIC RF680V2
DRAM: 2 GiB
***********************************************************
Development Device
***********************************************************
Core: 47 devices, 24 uclasses, devicetree: separate
MMC: mmc@fa10000: 0
Loading Environment from nowhere... OK
In: serial@2850000
Out: serial@2850000
Err: serial@2850000
Net: eth0: ethernet@8000000port@1
Initialize fTPM:
Unknown command 'tpm2' - try 'help'
Unknown command 'tpm2' - try 'help'
Hit any key to stop autoboot: 0
=>

0 oguzhan mutlu 3 months ago in reply to oguzhan mutlu

Prodigy 60 points

HARD RESET : **************** rates 13277755, index 1, size 8
SOFT RESET : **************** rates 13277755, index 1, size 8

0 Divyansh Mittal 3 months ago in reply to oguzhan mutlu

TI__Expert 8720 points

Hi,

oguzhan mutlu said:
ATF Mainline - master - 00f1ec6b8740ccd403e641131e294aabacf2a48b

OPTEE Mainline - 4.2.0 - 12d7c4ee4642d2d761e39fbcf21a06fb77141dea

These do not seem to be the latest.
To isolate the issue, can you please use the latest SDK and only replace the U-Boot there with mainline U-Boot and share the test results?

0 oguzhan mutlu 3 months ago in reply to Divyansh Mittal

Prodigy 60 points

Hi, I used prebuilt binaries (bl31, bl32) from TI SDK 11. Our console output is different than UART0 and there is no way to connect this port thats why you don't see any log messages from ATF or OPTEE. I made combination of the tests. I hope this help you.

################TI SDK OPTEE and ATF

U-Boot SPL 2025.04-00001-g102850fa9837-dirty (Jun 10 2025 - 09:19:25 +0300)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
**************** rates 13277755, index 1, size 8
Changed A53 CPU frequency to 1000000000Hz (S grade) in DT
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

################ TI SDK ATF, our custom OPTEE

U-Boot SPL 2025.04-00001-g102850fa9837-dirty (Jun 10 2025 - 08:59:15 +0300)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
**************** rates 13277755, index 1, size 8
Changed A53 CPU frequency to 1000000000Hz (S grade) in DT
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

I/TC:
I/TC: OP-TEE version: 4.2.0 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Thu Jan 1 01:00:00 UTC 1970 aarch64
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 ti_sci_init:486 Unable to communicate with control firmware (-65523)
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000f1978 failed
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 tee_otp_get_hw_unique_key:97 Could not get HUK
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000f19a8 failed
I/TC: Activated SA2UL device
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 sa2ul_init:106 Could not change TRNG firewall owner
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000f19b0 failed
E/TC:0 0
E/TC:0 0 Core data-abort at address 0x14 (translation fault)
E/TC:0 0 esr 0x96000005 ttbr0 0x9e992000 ttbr1 0x00000000 cidr 0x0
E/TC:0 0 cpu #0 cpsr 0x800003c4
E/TC:0 0 x0 000000009e8f6000 x1 0000000000000000
E/TC:0 0 x2 0000000000000000 x3 0000000000000000
E/TC:0 0 x4 0000000000000050 x5 000000009e982d70
E/TC:0 0 x6 ffffffffffffffb0 x7 000000000007fd20
E/TC:0 0 x8 000000009e982f80 x9 000000009e903000
E/TC:0 0 x10 0000000000000008 x11 000000009e993f30
E/TC:0 0 x12 0000000000000000 x13 000000009e993ec0
E/TC:0 0 x14 0000000000000000 x15 0000000000000000
E/TC:0 0 x16 000000009e81d848 x17 0000000000000000
E/TC:0 0 x18 0000000000000000 x19 000000009e994200
E/TC:0 0 x20 000000009e994208 x21 000000009e8f6000
E/TC:0 0 x22 000000009e8f6000 x23 000000009e8f6ea0
E/TC:0 0 x24 000000009e8f5d60 x25 0000000000000000
E/TC:0 0 x26 0000000000000000 x27 0000000000000000
E/TC:0 0 x28 0000000000000000 x29 000000009e994170
E/TC:0 0 x30 000000009e8180f8 elr 000000009e818108
E/TC:0 0 sp_el0 000000009e994170
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0 0x9e818108
E/TC:0 0 0x9e808aec
E/TC:0 0 0x9e8232d8
E/TC:0 0 0x9e808cb0
E/TC:0 0 Panic 'unhandled pageable abort' at core/arch/arm/kernel/abort.c:582 <abort_handler>
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0 0x9e808f98
E/TC:0 0 0x9e81fcdc
E/TC:0 0 0x9e80787c
E/TC:0 0 0x9e804a5c

################ Our custom ATF, TI SDK OPTEE

U-Boot SPL 2025.04-00001-g102850fa9837-dirty (Jun 10 2025 - 09:06:29 +0300)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
**************** rates 13277755, index 1, size 8
Changed A53 CPU frequency to 1000000000Hz (S grade) in DT
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE: BL31: v2.1 0(release):
NOTICE: BL31: Built : 01:00:00, Jan 1 1970
ERROR: Timeout waiting for thread SP_RESPONSE to fill
ERROR: Thread SP_RESPONSE verification failed (-60)
ERROR: Message receive failed (-60)
ERROR: Failed to get response (-60)
ERROR: Transfer send failed (-60)
ERROR: Timeout waiting for thread SP_RESPONSE to fill
ERROR: Thread SP_RESPONSE verification failed (-60)
ERROR: Message receive failed (-60)
ERROR: Failed to get response (-60)
ERROR: Transfer send failed (-60)
ERROR: Unable to query firmware capabilities (-60)

+1 Bin Liu 3 months ago in reply to oguzhan mutlu

TI__Guru**** 169011 points

Hi Oguzhan,

We are still working on replicating the issue, haven't seen the exact behavior yet.

Meanwhile,

oguzhan mutlu said:
U-Boot SPL 2025.04-00001-g102850fa9837-dirty (Jun 10 2025 - 09:19:25 +0300)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')

It seems the SYSFW you use is about two years old - v9.1.8. And I am not sure if you use the same v9.1.8 version of TIFS and DM firmware binaries either.

Can you please update both SYSFW binaries to those provided in SDK v11.0?

0 oguzhan mutlu 3 months ago in reply to Bin Liu

Prodigy 60 points

Hi, after updating TI-DM and TI-SYSFW binaries the problem seems fixed. I tried both hard and soft reset.

Thank you for all your help.

0 Bin Liu 3 months ago in reply to oguzhan mutlu

TI__Guru**** 169011 points

Hi Oguzhan,

Glad to hear the issue is resolved. Thanks for the update.

Processors

Processors forum

AM623: Fixup A53 CPU Frequency by Speed Grade Problem