R-car R8A7795 is unable to boot latest images

Affected images versions

v2024dev1 v2023 confirmed

Actual result

System hangs on boot

[    0.000325] NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.14
[    0.005892] NOTICE:  BL2: PRR is R-Car H3 Ver1.1
[    0.010468] NOTICE:  BL2: Board is Starter Kit Rev1.0
[    0.015483] NOTICE:  BL2: Boot device is HyperFlash(80MHz)
[    0.020922] NOTICE:  BL2: LCM state is CM
[    0.024899] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x52
[    0.031090] NOTICE:  BL2: DDR3200(rev.0.22)NOTICE:  [COLD_BOOT]NOTICE:  ..0
[    0.077178] NOTICE:  BL2: DRAM Split is 4ch
[    0.081063] NOTICE:  BL2: QoS is default setting(rev.0.35)
[    0.086564] NOTICE:  BL2: Lossy Decomp areas
[    0.090740] NOTICE:       Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
[    0.097825] NOTICE:       Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
[    0.104737] NOTICE:       Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
[    0.111652] NOTICE:  BL2: v1.3(release):4eef9a2
[    0.116141] NOTICE:  BL2: Built : 07:58:01, May 17 2017
[    0.121329] NOTICE:  BL2: Normal boot
[    0.124970] NOTICE:  BL2: dst=0xe6320190 src=0x8180000 len=512(0x200)
[    0.131519] NOTICE:  BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
[    0.137978] NOTICE:  BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
[    0.145204] NOTICE:  BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)
[    0.155683] NOTICE:  BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)


U-Boot 2023.01+dfsg-1+apertis7bv2024dev1b1 (Apr 11 2023 - 19:08:40 +0000)

CPU:   Renesas Electronics R8A7795 rev 1.1
Model: Renesas H3ULCB board based on r8a77950
DRAM:  896 MiB (effective 3.9 GiB)
Core:  64 devices, 21 uclasses, devicetree: fit
Flash: 0 Bytes
MMC:   sd@ee100000: 0, sd@ee140000: 1
Loading Environment from MMC... OK
In:    serial@e6e88000
Out:   serial@e6e88000
Err:   serial@e6e88000
Net:   
Error: ethernet@e6800000 address not set.
No ethernet found.

Auto-update from TFTP: failed, env. variable 'updatefile' not found
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
U-Boot menu
1:      Apertis v2024dev1 6.1.0-7-arm64
2:      Apertis v2024dev1 6.1.0-7-arm64 (rescue target)
Enter choice: 1:        Apertis v2024dev1 6.1.0-7-arm64
Retrieving file: /initrd.img-6.1.0-7-arm64
Retrieving file: /vmlinuz-6.1.0-7-arm64
append: root=UUID=13eee81f-1657-4580-ab1e-606f9876daf4 rootwait rw quiet splash plymouth.ignore-serial-consoles fsck.mode=auto fsck.repair=yes
Retrieving file: /dtbs/6.1.0-7-arm64/renesas/r8a77950-ulcb.dtb
## Flattened Device Tree blob at 48080000
   Booting using the fdt blob at 0x48080000
Working FDT set to 48080000
   Using Device Tree in place at 0000000048080000, end 0000000048094251
Working FDT set to 48080000
Overlap found: 0x500000000..0x53fffffff / 0x500000000..0x53fffffff
Overlap found: 0x600000000..0x63fffffff / 0x600000000..0x63fffffff
Overlap found: 0x700000000..0x73fffffff / 0x700000000..0x73fffffff

Starting kernel ...

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

1. ✅ always
2. often, but not always
3. rarely

Impact of bug

Board in unbootable

Attachments

Add further information about the environment in the form of attachments here. Attach plain text files from log output (from journalctl, systemctl, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.

Screenshots and videos are usually useful for graphic issues.

Root cause

This needs to be confirmed but likely this is an issue due to memory overlap between kernel, dtb and initramfs

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @sagar @sudarshan @wlozano r

Phabricator link: https://phabricator.apertis.org/T9795