TDA4VH-Q1: TDA4VH hs-fs eMMC boot failed, USB DFU upgrade failed

Tank.Xue

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VH, UNIFLASH

Tool/software:

Hi TI Experts,

We have a TDA4VH HS-FS board, and eMMC boot failed. The log shows: "Loading Environment from MMC... parent transid verify failed on 1114112 wanted 27 found 1".

The logs are shown below:

U-Boot SPL 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)
EEPROM board info checksum mismatch (Calculated: 0x != Expected: 0x)
Error: No board info detected (error -14)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 17 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):7cd03a79
NOTICE:  BL31: Built : 16:00:04, Apr 29 2024
I/TC:
I/TC: No non-secure external DT
I/TC: OP-TEE version: a094d533 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Mon Apr 29 15:59:22 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: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (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 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
Trying to boot from MMC1
Authentication passed
Authentication passed


U-Boot 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)

SoC:   J784S4 SR1.0 HS-FS
Model: KUKA KR C5 basic-2 (J784S4)
Board: J784S4-krc5-basic2 rev E1
DRAM:  2 GiB (effective 4 GiB)
Core:  104 devices, 32 uclasses, devicetree: separate
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from MMC... parent transid verify failed on 1114112 wanted 27 found 1
parent transid verify failed on 1114112 wanted 27 found 1
Ignoring transid failure
"Synchronous Abort" handler, esr 0x8600000d
elr: ffffffff808f4000 lr : 0000000080826ca0 (reloc)
elr: 0000000000000000 lr : 00000000fff32ca0
x0 : 0000000000000000 x1 : 00000000fdd6a618
x2 : 0000000000000000 x3 : 0000000000000020
x4 : 0000000000000034 x5 : 00000000fdd6a62f
x6 : 0000000000000000 x7 : 00000000fdd6aa60
x8 : 00000000ffffffe0 x9 : 0000000000000008
x10: 000000000000000d x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8bda0 x19: 000000000000001f
x20: 0000000000000002 x21: 00000000fde98da0
x22: 0000000000000000 x23: 0000000000000001
x24: 000000000000001e x25: 00000000fdd6ad88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6a5b0

Code: "Synchronous Abort" handler, esr 0x96000004
elr: 0000000080802a98 lr : 0000000080802a98 (reloc)
elr: 00000000fff0ea98 lr : 00000000fff0ea98
x0 : 0000000000000006 x1 : 0000000000000000
x2 : 0000000000000020 x3 : 0000000002820000
x4 : 0000000002820000 x5 : 00000000fdd69fbb
x6 : 00000000fffb569d x7 : 00000000fdd6a440
x8 : 00000000ffffffe8 x9 : 0000000000000008
x10: 0000000000000010 x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8bda0 x19: fffffffffffffffc
x20: 00000000fffbdb14 x21: 00000000fffb60ae
x22: 00000000fffbf357 x23: 0000000000000000
x24: 000000000000001e x25: 00000000fdd6ad88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6a440

Code: 92800073 b0000580 910ed800 940270c9 (b8737ae1)
Resetting CPU ...

resetting ...

U-Boot SPL 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)
EEPROM board info checksum mismatch (Calculated: 0x != Expected: 0x)
Error: No board info detected (error -14)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 17 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):7cd03a79
NOTICE:  BL31: Built : 16:00:04, Apr 29 2024
I/TC:
I/TC: No non-secure external DT
I/TC: OP-TEE version: a094d533 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Mon Apr 29 15:59:22 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: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (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 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
Trying to boot from MMC1
Authentication passed
Authentication passed


U-Boot 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)

SoC:   J784S4 SR1.0 HS-FS
Model: KUKA KR C5 basic-2 (J784S4)
Board: J784S4-krc5-basic2 rev E1
DRAM:  2 GiB (effective 4 GiB)
Core:  104 devices, 32 uclasses, devicetree: separate
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from MMC... parent transid verify failed on 1114112 wanted 27 found 1
parent transid verify failed on 1114112 wanted 27 found 1
Ignoring transid failure
"Synchronous Abort" handler, esr 0x8600000d
elr: ffffffff808f4000 lr : 0000000080826ca0 (reloc)
elr: 0000000000000000 lr : 00000000fff32ca0
x0 : 0000000000000000 x1 : 00000000fdd6a618
x2 : 0000000000000000 x3 : 0000000000000020
x4 : 0000000000000034 x5 : 00000000fdd6a62f
x6 : 0000000000000000 x7 : 00000000fdd6aa60
x8 : 00000000ffffffe0 x9 : 0000000000000008
x10: 000000000000000d x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8bda0 x19: 000000000000001f
x20: 0000000000000002 x21: 00000000fde98da0
x22: 0000000000000000 x23: 0000000000000001
x24: 000000000000001e x25: 00000000fdd6ad88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6a5b0

Code: "Synchronous Abort" handler, esr 0x96000004
elr: 0000000080802a98 lr : 0000000080802a98 (reloc)
elr: 00000000fff0ea98 lr : 00000000fff0ea98
x0 : 0000000000000006 x1 : 0000000000000000
x2 : 0000000000000020 x3 : 0000000002820000
x4 : 0000000002820000 x5 : 00000000fdd69fbb
x6 : 00000000fffb569d x7 : 00000000fdd6a440
x8 : 00000000ffffffe8 x9 : 0000000000000008
x10: 0000000000000010 x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8bda0 x19: fffffffffffffffc
x20: 00000000fffbdb14 x21: 00000000fffb60ae
x22: 00000000fffbf357 x23: 0000000000000000
x24: 000000000000001e x25: 00000000fdd6ad88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6a440

Code: 92800073 b0000580 910ed800 940270c9 (b8737ae1)
Resetting CPU ...

resetting ...

U-Boot SPL 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)
EEPROM board info checksum mismatch (Calculated: 0x != Expected: 0x)
Error: No board info detected (error -14)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 17 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):7cd03a79
NOTICE:  BL31: Built : 16:00:04, Apr 29 2024
I/TC:
I/TC: No non-secure external DT
I/TC: OP-TEE version: a094d533 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Mon Apr 29 15:59:22 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: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (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 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
Trying to boot from MMC1
Authentication passed
Authentication passed


U-Boot 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)

SoC:   J784S4 SR1.0 HS-FS
Model: KUKA KR C5 basic-2 (J784S4)
Board: J784S4-krc5-basic2 rev E1
DRAM:  2 GiB (effective 4 GiB)
Core:  104 devices, 32 uclasses, devicetree: separate
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from MMC... parent transid verify failed on 1114112 wanted 27 found 1
parent transid verify failed on 1114112 wanted 27 found 1
Ignoring transid failure
"Synchronous Abort" handler, esr 0x8600000d
elr: ffffffff808f4000 lr : 0000000080826ca0 (reloc)
elr: 0000000000000000 lr : 00000000fff32ca0
x0 : 0000000000000000 x1 : 00000000fdd6a618
x2 : 0000000000000000 x3 : 0000000000000020
x4 : 0000000000000034 x5 : 00000000fdd6a62f
x6 : 0000000000000000 x7 : 00000000fdd6aa60
x8 : 00000000ffffffe0 x9 : 0000000000000008
x10: 000000000000000d x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8bda0 x19: 000000000000001f
x20: 0000000000000002 x21: 00000000fde98da0
x22: 0000000000000000 x23: 0000000000000001
x24: 000000000000001e x25: 00000000fdd6ad88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6a5b0

Code: "Synchronous Abort" handler, esr 0x96000004
elr: 0000000080802a98 lr : 0000000080802a98 (reloc)
elr: 00000000fff0ea98 lr : 00000000fff0ea98
x0 : 0000000000000006 x1 : 0000000000000000
x2 : 0000000000000020 x3 : 0000000002820000
x4 : 0000000002820000 x5 : 00000000fdd69fbb
x6 : 00000000fffb569d x7 : 00000000fdd6a440
x8 : 00000000ffffffe8 x9 : 0000000000000008
x10: 0000000000000010 x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8bda0 x19: fffffffffffffffc
x20: 00000000fffbdb14 x21: 00000000fffb60ae
x22: 00000000fffbf357 x23: 0000000000000000
x24: 000000000000001e x25: 00000000fdd6ad88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6a440

Code: 92800073 b0000580 910ed800 940270c9 (b8737ae1)
Resetting CPU ...

resetting ...

U-Boot SPL 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)
EEPROM board info checksum mismatch (Calculated: 0x != Expected: 0x)
Error: No board info detected (error -14)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
SPL initial stack usage: 13440 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 17 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):7cd03a79
NOTICE:  BL31: Built : 16:00:04, Apr 29 2024
I/TC:
I/TC: No non-secure external DT
I/TC: OP-TEE version: a094d533 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Mon Apr 29 15:59:22 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: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (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 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
Trying to boot from MMC1
Authentication passed
Authentication passed


U-Boot 2023.04-kdeb12u36 (Jul 04 2024 - 07:05:47 +0000)

SoC:   J784S4 SR1.0 HS-FS
Model: KUKA KR C5 basic-2 (J784S4)
Board: J784S4-krc5-basic2 rev E1
DRAM:  2 GiB (effective 4 GiB)
Core:  104 devices, 32 uclasses, devicetree: separate
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from MMC... parent transid verify failed on 1114112 wanted 27 found 1
parent transid verify failed on 1114112 wanted 27 found 1
Ignoring transid failure
"Synchronous Abort" handler, esr 0x8600000d
elr: ffffffff808f4000 lr : 0000000080826ca0 (reloc)
elr: 0000000000000000 lr : 00000000fff32ca0
x0 : 0000000000000000 x1 : 00000000fdd6a618
x2 : 0000000000000000 x3 : 0000000000000020
x4 : 0000000000000034 x5 : 00000000fdd6a62f
x6 : 0000000000000000 x7 : 00000000fdd6aa60
x8 : 00000000ffffffe0 x9 : 0000000000000008
x10: 000000000000000d x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8bda0 x19: 000000000000001f
x20: 0000000000000002 x21: 00000000fde98da0
x22: 0000000000000000 x23: 0000000000000001
x24: 000000000000001e x25: 00000000fdd6ad88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6a5b0

Code: "Synchronous Abort" handler, esr 0x96000004
elr: 0000000080802a98 lr : 0000000080802a98 (reloc)
elr: 00000000fff0ea98 lr : 00000000fff0ea98
x0 : 0000000000000006 x1 : 0000000000000000
x2 : 0000000000000020 x3 : 0000000002820000
x4 : 0000000002820000 x5 : 00000000fdd69fbb
x6 : 00000000fffb569d x7 : 00000000fdd6a440
x8 : 00000000ffffffe8 x9 : 0000000000000008
x10: 0000000000000010 x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8bda0 x19: fffffffffffffffc
x20: 00000000fffbdb14 x21: 00000000fffb60ae
x22: 00000000fffbf357 x23: 0000000000000000
x24: 000000000000001e x25: 00000000fdd6ad88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6a440

Code: 92800073 b0000580 910ed800 940270c9 (b8737ae1)
Resetting CPU ...

resetting ...

We tried upgrading using USB DFU mode, but it failed too. It seems to be stuck at "u-boot starting".

The same error log also appeared during the DFU upgrade: "Loading environment from MMC...Parent trans ID verify failed, expected 27, got 1".

Here are more DFU log from UART.

U-Boot SPL 2023.04-kdeb12u44 (Sep 10 2024 - 06:14:27 +0000)
Board ID EEPROM checksum: mismatch (Calculated: 0x652d544c != Expected: 0xffffffff)
Board type: KR C5 basic-2 (FP)
ddrss node to fixup: memorycontroller@2990000
ddrss node to fixup: memorycontroller@29b0000
ddrss node to fixup: memorycontroller@29d0000
ddrss node to fixup: memorycontroller@29f0000
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
ECC is enabled, priming DDR which will take several seconds.
ECC: priming DDR completed in 1293 msec
SPL initial stack usage: 13440 bytes
Trying to boot from DFU
#####DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 18 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):kuka/debian/dufourspitze/trustedfirmware-krc5/2.10.0-kdeb12u1
NOTICE:  BL31: Built : 16:00:04, Apr 29 2024
I/TC:
I/TC: No non-secure external DT
I/TC: OP-TEE version: kuka/debian/dufourspitze/optee-os-krc5/4.1.0-kdeb12u1 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Mon Apr 29 15:59:22 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: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (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 2023.04-kdeb12u44 (Sep 10 2024 - 06:14:27 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
Trying to boot from DFU
cdns-usb3-peripheral usb@6000000: DRD version v1 (ID: 0004024e, rev: 00000200)
cdns-usb3-peripheral usb@6000000: Initialized  ep0 support:
cdns-usb3-peripheral usb@6000000: Initialized  ep1out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep2out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep3out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep4out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep5out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep6out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep7out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep8out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep9out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep10out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep11out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep12out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep13out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep14out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep15out support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep1in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep2in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep3in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep4in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep5in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep6in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep7in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep8in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep9in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep10in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep11in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep12in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep13in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep14in support: BULK, INT ISO
cdns-usb3-peripheral usb@6000000: Initialized  ep15in support: BULK, INT ISO
####DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed


U-Boot 2023.04-kdeb12u44 (Sep 10 2024 - 06:14:27 +0000)

SoC:   J784S4 SR1.0 HS-FS
Model: KUKA KR C5 basic-2 (J784S4)
Board: J784S4-krc5-basic2 rev E1
DRAM:  2 GiB (effective 3.5 GiB)
Core:  104 devices, 32 uclasses, devicetree: separate
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from MMC... parent transid verify failed on 1114112 wanted 27 found 1
parent transid verify failed on 1114112 wanted 27 found 1
Ignoring transid failure
"Synchronous Abort" handler, esr 0x8600000d
elr: ffffffff808f3000 lr : 0000000080826944 (reloc)
elr: 0000000000000000 lr : 00000000fff33944
x0 : 0000000000000000 x1 : 00000000fdd6b618
x2 : 0000000000000000 x3 : 0000000000000020
x4 : 0000000000000034 x5 : 00000000fdd6b62f
x6 : 0000000000000000 x7 : 00000000fdd6ba60
x8 : 00000000ffffffe0 x9 : 0000000000000008
x10: 000000000000000d x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8cda0 x19: 000000000000001f
x20: 0000000000000002 x21: 00000000fde99da0
x22: 0000000000000000 x23: 0000000000000001
x24: 000000000000001e x25: 00000000fdd6bd88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6b5b0

Code: "Synchronous Abort" handler, esr 0x96000004
elr: 0000000080802a98 lr : 0000000080802a98 (reloc)
elr: 00000000fff0fa98 lr : 00000000fff0fa98
x0 : 0000000000000006 x1 : 0000000000000000
x2 : 0000000000000020 x3 : 0000000002820000
x4 : 0000000002820000 x5 : 00000000fdd6afbb
x6 : 00000000fffb6120 x7 : 00000000fdd6b440
x8 : 00000000ffffffe8 x9 : 0000000000000008
x10: 0000000000000010 x11: 0000000000000006
x12: 000000000001869f x13: 00000000000000e6
x14: 000000000000000e x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000fde8cda0 x19: fffffffffffffffc
x20: 00000000fffbe40e x21: 00000000fffb6b31
x22: 00000000fffbfc51 x23: 0000000000000000
x24: 000000000000001e x25: 00000000fdd6bd88
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fdd6b440

Code: 92800073 90000580 9132c000 94026fa8 (b8737ae1)
Resetting CPU ...

resetting ...

DFU execute log on PC terminal:

tank@Tank:~/Downloads/dfu/krc5-2_3.3_dfu$ sudo ./boot_dfu krc5-basic2 hs-fs
[sudo] password for tank: 
Trying to rescue krc5-basic2 controller with hs-fs SoC ...
###############
### R5F SPL ###
###############
Waiting for device 'bootloader' to be available...
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6167
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 512
Copying data from PC to DFU device
Download	[=========================] 100%       405970 bytes
Download done.
Sent a total of 405970 bytes
state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
dfu-util: can't detach
Resetting USB to switch back to runtime mode
###############
### A72 SPL ###
###############
Waiting for device 'tispl.bin' to be available...
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6168
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download	[=========================] 100%      1297595 bytes
Download done.
Sent a total of 1297595 bytes
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
Resetting USB to switch back to runtime mode
##################
### A72 u-boot ###
##################
Waiting for device 'u-boot.img' to be available...
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6168
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download	[=========================] 100%      1014891 bytes
Download done.
Sent a total of 1014891 bytes
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
Resetting USB to switch back to runtime mode
######################
### Rescue System ###
#####################
Waiting for device 'rescue.fit' to be available...

Can you please advise on how to troubleshoot this issue? Tks!

8 months ago

0 Gokul Praveen 8 months ago

TI__Genius 10570 points

HI Tanx,

Could you help us with a couple of questions:

1:What is the the linux sdk version you are using?

2:Is it a custom board or TI EVM?

Regards

Gokul

0 Tank.Xue 8 months ago in reply to Gokul Praveen

Prodigy 90 points

Hi Gokul

1. The version of the Linux SDK we are using is: 09.02.00.05.

2. It is a custom board.

By the way, we only have this board with this issue, other boards do not have this issue.

Best Regards

Tank

0 Gokul Praveen 8 months ago in reply to Tank.Xue

TI__Genius 10570 points

HI Tank,

Thanks for the info.Just wanted to have more info on the following as well:

1:Have you tried booting using a GP device .

2:Are you facing the same issue in SD BOOT mode.

3:Is it the first time you are bringing up the board or is it that you have tested it earlier and it was working earlier.

0 Tank.Xue 8 months ago in reply to Gokul Praveen

Prodigy 90 points

Hi Gokul

Thanks for your reply.

1.Yes, we've tried booting with the GP device, but it can not boot either.

Because this board is installed with an HS-FS device, which can also be identified as an HS-FS device using the uart-parser tool.

2.Sorry, our board do not yet support SD boot mode.

3.This board has been successfully used for some time with eMMC boot mode.

After re-flashing the eMMC once, this board can no longer boot from eMMC and always gets stuck before entering Uboot.

BTW,

We tried to use the UNIFLASH tool to flash the EMMC, but it was not successful.

Best Regards!

Tank

0 Gokul Praveen 8 months ago in reply to Tank.Xue

TI__Genius 10570 points

Hi Tank,

From the logs,it is most likely a corrupted filesystem caused while reflashing.Reformatting the emmc and reflashing should ideally solve the problem.Can you try that.

Regards

Gokul

0 Tank.Xue 8 months ago in reply to Gokul Praveen

Prodigy 90 points

Hi Gokul

Please tell me how to reformat and reflash the eMMC?

I've tried to format the eMMC using the Uniflash utility and UART boot mode, but neither of them worked and it seems to be stuck in U-BOOT starting.

Is there any other way to do this?

Best Regards!

Tank

0 Gokul Praveen 8 months ago in reply to Tank.Xue

TI__Genius 10570 points

Hi Tank,

Are you able to enter into UBOOT terminal using UART BOOT mode?

0 Tank.Xue 8 months ago in reply to Gokul Praveen

Prodigy 90 points

Hi Gokul

Using UART BOOT mode was also unsuccessful.

I followed the steps in the <TDA4VM-UART-Boot-faq> guide. But it's stuck on loading the tispl.bin file.

7024.TDA4VM-UART-Boot-faq.pdf

ps: The TDA4VH does not require a separate sysfw.itb file, so the above steps do not require loading the sysfw.itb file.

Best Regards

Tank

0 Tank.Xue 8 months ago in reply to Gokul Praveen

Prodigy 90 points

Hi Gokul

“it is most likely a corrupted filesystem caused while reflashing.”

Question:If the file system is corrupted, Why can't I fix it using USB-DFU mode?

Best Regards

Tank

0 Gokul Praveen 8 months ago in reply to Tank.Xue

TI__Genius 10570 points

Hi Tank,

Tank.Xue said:
Question:If the file system is corrupted, Why can't I fix it using USB-DFU mode?

The issue is happening when the print "Loading environment from MMC..parent transid verify failed" occurs,which means that irrespective of the initial mode it uses for booting,at UBOOT stage it is trying to load the environment configurations from the MMC boot partition which is corrupted, hence causing the error.

Tank,can you try with the latest SDK and check if this issue is there

0 Tank.Xue 7 months ago in reply to Gokul Praveen

Prodigy 90 points

Hi Gokul

I would like to update some information:

For this board, we removed the eMMC chip on the board, and erased it using an offline burner. Then we reinstalled it back onto the board.

The board can then be re-flashed using the DFU tool and will start up normally after the re-flash.

Therefore, I have a question: what kind of file system corruption would cause such a crash (that even DFU cannot recover)?

In addition,it was found from the log that during the DFU process, it is necessary to “loading environment from MMC” and then determine whether the "No eMMC boot device is active" or whether the card is responding.

It seems that the success of DFU depends on the content of eMMC.

Is this caused by the u-boot.img file downloaded into the system?
Can it be changed to skip "Loading Environment from MMC" and directly"using default environment"?
This may avoid this issue. Do you think so?

Best Regards!

Tank

0 Gokul Praveen 7 months ago in reply to Tank.Xue

TI__Genius 10570 points

i Tank,

Tank.Xue said:
Therefore, I have a question: what kind of file system corruption would cause such a crash (that even DFU cannot recover)?

It can be caused due to variety of reasons like :

Logical bugs: The filesystem structures haven’t been properly updated and stored correctly.
Misdirected writes: the underlying storage does not store the data to the exact address as expected and overwrites some other data.
Block storage device (hardware or emulated) does not properly flush and persist data between transactions so they get mixed up.
Lost writes without proper error handling: writing the block worked as viewed on the filesystem layer, but there was a problem on the lower layers not propagated upwards.
Suspend mode sometimes confuse the kernel, drive cache, etc, leading to data loss causing same type of errors.

Also , are you using btrfs filesystem for eMMC ?

Tank.Xue said:
Is this caused by the u-boot.img file downloaded into the system?
Can it be changed to skip "Loading Environment from MMC" and directly"using default environment"?
This may avoid this issue. Do you think so?

Yes,skipping Loading Environment from MMC can solve the issue.

Can you try applying the changes mentioned below and recompile UBoot . On doing this,you can skip "Loading Environment from MMC".

Processors

Processors forum

TDA4VH-Q1: TDA4VH hs-fs eMMC boot failed, USB DFU upgrade failed