Hi All, On Wed, 26 Jun 2024 at 21:07, Sam Protsenko <semen.protse...@linaro.org> wrote: > > On Wed, Jun 26, 2024 at 10:15 AM Anand Moon <linux.am...@gmail.com> wrote: > > > > Fix the issue where CONFIG_SYS_BOARD was incorrectly set on > > Odroid XU3 boards, causing boot failure. This was resolved by > > correcting the SYS_BOARD entry in Kconfig to load the correct > > device tree source (dts) for the Odroid Exynos5422 Platforms. > > > > Fixes: f76750d11133 ("Convert CONFIG_CONS_INDEX et al to Kconfig") > > Signed-off-by: Anand Moon <linux.am...@gmail.com> > > --- > > U-Boot 2024.07-rc5-00042-g80a111f426 (Jun 26 2024 - 15:03:09 +0530) for > > ODROID-XU3/XU4/HC1/HC2 > > > > CPU: Exynos5422 @ 800 MHz > > DRAM: 2 GiB > > Core: 74 devices, 12 uclasses, devicetree: separate > > MMC: mmc@12200000: 0, mmc@12220000: 2 > > Loading Environment from MMC... Reading from MMC(2)... *** 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(2) > > Net: No ethernet found. > > Hit any key to stop autoboot: 0 > > switch to partitions #0, OK > > mmc2 is current device > > Scanning mmc 2:1... > > Found U-Boot script /boot/boot.scr > > 2046 bytes read in 22 ms (90.8 KiB/s) > > 8104280 bytes read in 519 ms (14.9 MiB/s) > > Failed to load '/boot/dtbs/exynos5422-smdk5420xu4.dtb' > > SCRIPT FAILED: continuing... > > No EFI system partition > > No EFI system partition > > Failed to persist EFI variables > > No EFI system partition > > Failed to persist EFI variables > > No EFI system partition > > Failed to persist EFI variables > > Loading Boot0000 'mmc 2' failed > > EFI boot manager: Cannot load any image > > MMC Device 1 not found > > no mmc device at slot 1 > > --- > > Reviewed-by: Sam Protsenko <semen.protse...@linaro.org> > Thanks
Gentle ping? Thanks -Anand