TDA4VM: The boot process is stuck at U-Boot.

Hi all

The repeated occurrence of ti_sci_get_response: Message receive failed. ret = -110 indicates that U-Boot is unable to receive a response from the System Control Firmware (SYSFW) within the expected timeframe.

Is it possible that SYSFW has not started or has crashed?

And how can it be verified?

BR

liupt

Hi Gibbs

(1) What's your boot mode?----》XSPI+Norflash

(2) What's the log for normal boot board look like? Could you provide it?

Normal:
U-Boot SPL 2024.04-ti-g4f08d2427322 (May 13 2025 - 01:03:25 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
Trying to boot from SPI
Error: Boot MCU1_0 from the default partition: A!   
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also enc
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also enc
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also enc
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also enc
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also enc
Loading Environment from nowhere... OK
Starting ATF on ARM64 core...
] 
NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
I/TC: 
I/TC: OP-TEE version: 4.2.0-dev (gcc version 13.3.0 (GCC)) #1 Fri Apr 12 09:51:21 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
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: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP 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 2024.04-ti-g4f08d2427322 (Jun 25 2025 - 08:26:45 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from SPI
k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled
jedec_spi_nor flash@0: non-uniform erase sector maps are not supported yet.
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also enc
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also enc


U-Boot 2024.04-ti-g4f08d2427322 (Jun 25 2025 - 08:26:45 +0000)

SoC:   J721E SR2.0 GP
Model: Texas Instruments J721e EVM
Board: J721EX-PM2-SOM rev E8
DRAM:  2 GiB (effective 4 GiB)
Core:  115 devices, 34 uclasses, devicetree: separate
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from nowhere... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA00101 cpsw_ver: 0x6BA80100 ale_ver: 0x00293904 Ports:1
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
Net:   PHY PassiveMode: 0x0000 
eth0: ethernet@46000000port@1
k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled
jedec_spi_nor flash@0: non-uniform erase sector maps are not supported yet.
SF: Detected s28hs512t with page size 256 Bytes, erase size 256 KiB, total 64 MiB
device 0 offset 0x680000, size 0x9
SF: 9 bytes @ 0x680000 Read: OK
Error: Invalid flag byte at 0x80000000. Value: 0xFF
Hit any key to stop autoboot:  0 
Device at ufs@4e84000 up at:cdns-ufs-pltfm ufs@4e84000: [RX, TX]: gear=[3, 3], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 2
scanning bus for devices...
  Device 0: (0:0) Vendor: SAMSUNG Prod.: KLUEGAJ1ZD-B0CQ Rev: 5900
            Type: Hard Disk
            Capacity: 241183.9 MB = 235.5 GB (61743103 x 4096)
  Device 1: (0:1) Vendor: SAMSUNG Prod.: KLUEGAJ1ZD-B0CQ Rev: 5900
            Type: Hard Disk
            Capacity: 31.9 MB = 0.0 GB (8191 x 4096)
  Device 2: (0:2) Vendor: SAMSUNG Prod.: KLUEGAJ1ZD-B0CQ Rev: 5900
            Type: Hard Disk
            Capacity: 31.9 MB = 0.0 GB (8191 x 4096)

Device 0: (0:0) Vendor: SAMSUNG Prod.: KLUEGAJ1ZD-B0CQ Rev: 5900
            Type: Hard Disk

Bug:
U-Boot SPL 2024.04-ti-g4f08d2427322 (May 13 2025 - 01:03:25 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
Trying to boot from SPI
Error: Boot MCU1_0 from the default partition: A!   
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
Starting ATF on ARM64 core...
] 
NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
I/TC: 
I/TC: OP-TEE version: 4.2.0-dev (gcc version 13.3.0 (GCC)) #1 Fri Apr 12 09:51:21 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
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: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP 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 2024.04-ti-g4f08d2427322 (Jun 25 2025 - 08:26:45 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from SPI
k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled
jedec_spi_nor flash@0: non-uniform erase sector maps are not supported yet.
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted


U-Boot 2024.04-ti-g4f08d2427322 (Jun 25 2025 - 08:26:45 +0000)

SoC:   J721E SR2.0 GP
Model: Texas Instruments J721e EVM
Board: J721EX-PM2-SOM rev E8
DRAM:  2 GiB (effective 4 GiB)
Core:  115 devices, 34 uclasses, devicetree: separate
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from nowhere... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA00101 cpsw_ver: 0x6BA80100 ale_ver: 0x00293904 Ports:1
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
Net:   PHY PassiveMode: 0x0000 
eth0: ethernet@46000000port@1
k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled
jedec_spi_nor flash@0: non-uniform erase sector maps are not supported yet.
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
ti-udma dma-controller@285c0000: tisci tx alloc failed -110
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI ring free fail (-110) ring_idx 2
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI ring free fail (-110) ring_idx 96
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI config ring fail (-110) ring_idx 2
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI config ring fail (-110) ring_idx 96
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI config ring fail (-110) ring_idx 2
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI config ring fail (-110) ring_idx 96
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI config ring fail (-110) ring_idx 2
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI config ring fail (-110) ring_idx 96
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI config ring fail (-110) ring_idx 2
ti_sci system-controller@44083000: ti_sci_get_response: Message receive failed. ret = -110
k3-navss-ringacc ringacc@2b800000: TISCI config ring fail (-110) ring_idx 96

(3) How do you program your sysfw? ---》

(4) How many customized board do you test? Does each board have the same issue? ---->Many boards were only found this time.

(5) How frequently does it happen? Does it have any special test pattern?---》There are no specific test patterns for heat maturity; it has occurred very rarely and has only been encountered once.

BR

liupt

Hi 

How do you program your sysfw? ---》 How to modify the sysfw？

BR

liupt

Hi,

Does this work stably with older sdk?

Regards,
Tanmay

Hi, Liupt

Few question, double check

(1) Did you do "OSPI Controller PHY Tuning" on your board?

https://www.ti.com/lit/an/spract2/spract2.pdf?ts=1752665046897&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FTDA4VM%253FkeyMatch%253Dtda4%2526tisearch%253Duniversal_search%2526usecase%253Dpartmatches

(2) Did you do phy calibration for this board?

 TDA4VM: ospi clock problem 

Thank You.

Gibbs

Hi gibbs

I don't quite understand how this is related to the OSPI PHY. Isn't the uboot hang caused by the ti_sci issue?

What feedback has TI's technical team provided regarding this issue?

BR

liupt

Hi gibbs

We don't test it on old sdk，so we have nothing abot.

Regarding the OSPI PHY issue you mentioned, does it refer to the PHY file burned into the last partition of the NOR flash?
If not, how can we test whether it has any issues?

BR
liupt

Hi gibbs

The current OSPI frequency is 25MHz, which is a very low speed, so PHY tuning should not be necessary.

flash@0 {
compatible = "jedec,spi-nor";
reg = <0x0>;
spi-tx-bus-width = <8>;
spi-rx-bus-width = <8>;
spi-max-frequency = <25000000>;
cdns,tshsl-ns = <60>;
cdns,tsd2d-ns = <60>;
cdns,tchsh-ns = <60>;
cdns,tslch-ns = <60>;
cdns,read-delay = <4>;

BR

liupt

Hi, Liupt

I found one error is very strange. Most OSPI flash boot failed has similar error log.

k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled
jedec_spi_nor flash@0: non-uniform erase sector maps are not supported yet.

Does normal boot have same error context?

Ref.

 TDA4VM: SK-TDA4VM OSPI issue 

Thanks

Gibbs