Bug#1012269: u-boot-exynos on Odroid XU4 searches for exynos5422-smdk5420xu4.dtb instead of exynos5422-odroidxu4.dtb

[Jochen Sprickerhof]

Hi Vagrant,

* Vagrant Cascadian <vagr...@debian.org> [2022-11-04 14:22]:

On 2022-06-02, Jochen Sprickerhof wrote:

with the latest u-boot-exynos in unstable it tries to load
exynos5422-smdk5420xu4.dtb whereas linux-image-5.17.0-3-armmp only
contains exynos5422-odroidxu4.dtb. This was not the case with 2022.01+dfsg-2:

U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 21:25:25 +0000) for 
ODROID-XU3/XU4/HC1/HC2
[..]
Retrieving file: /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-smdk5420xu4.dtb
** File not found 
/usr/lib/linux-image-5.17.0-3-armmp/exynos5422-smdk5420xu4.dtb **

U-Boot 2022.01+dfsg-2 (Jan 26 2022 - 19:58:27 +0000) for ODROID-XU3/XU4/HC1/HC2
[..]
Retrieving file: /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-odroidxu4.dtb

Thanks for bringing this up in IRC.

My guess is this was broken in 2022.04, and fixed in 2022.07-rc5 with
this commit:

[..]

Could you test 2022.10 from unstable and/or pull 2022.07 from
snapshots.debian.org and test it?

U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +0000) for ODROID-XU3/XU4/HC1/HC2

CPU:   Exynos5422 @ 800 MHz
DRAM:  2 GiB
Core:  73 devices, 12 uclasses, devicetree: separate
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Odroid XU3/XU4/HC1/HC2 based on Exynos5422
Type:  xu4
Boot device: MMC(0)
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
MMC Device 1 not found
no mmc device at slot 1
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
U-Boot menu
1:      Debian GNU/Linux bookworm/sid 6.0.0-6-armmp
2:      Debian GNU/Linux bookworm/sid 6.0.0-6-armmp (rescue target)
3:      Debian GNU/Linux bookworm/sid 5.18.0-2-armmp
4:      Debian GNU/Linux bookworm/sid 5.18.0-2-armmp (rescue target)
Enter choice: 1:        Debian GNU/Linux bookworm/sid 6.0.0-6-armmp
Retrieving file: /boot/initrd.img-6.0.0-6-armmp
Retrieving file: /boot/vmlinuz-6.0.0-6-armmp
append: root=LABEL=mmcroot rw quiet mitigations=off
Retrieving file: /usr/lib/linux-image-6.0.0-6-armmp/exynos5422-smdk5420xu4.dtb
** File not found /usr/lib/linux-image-6.0.0-6-armmp/exynos5422-smdk5420xu4.dtb 
**
Kernel image @ 0x42000000 [ 0x000000 - 0x4f3200 ]
## Flattened Device Tree blob at b99684d0
   Booting using the fdt blob at 0xb99684d0
   Loading Ramdisk to 4f3a5000, end 4fffff7f ... OK
   Loading Device Tree to 4f39e000, end 4f3a49a7 ... OK

Starting kernel ...

The workaround with:

ln -s exynos5422-odroidxu4.dtb exynos5422-smdk5420xu4.dtb

works.

Cheers Jochen

I finally found time to test, sorry for the delay. Still the same problem:

signature.asc
Description: PGP signature