hi,
finally got around to do it: added "board=ordoid" to
CONFIG_EXTRA_ENV_SETTINGS in include/configs/odroid_xu3.h using
following patch, rebuild the rpm locally, updated u-boot on the sdcard
for my local odroid-hc2 and booted with the new u-boot ... so adding
board to CONFIG_EXTRA_ENV_SETTINGS fixes the problem.
Gabriel
-----------------------------------------------------------------------------
diff -u -r u-boot-2021.10/include/configs/odroid_xu3.h
u-boot-2021.10-mod/include/configs/odroid_xu3.h
--- u-boot-2021.10/include/configs/odroid_xu3.h 2022-06-08
10:56:19.361113780 +0300
+++ u-boot-2021.10-mod/include/configs/odroid_xu3.h 2022-06-08
10:53:10.834233375 +0300
@@ -94,6 +94,7 @@
"rootfstype=ext4\0" \
"console=console=ttySAC2,115200n8\0" \
"fdtfile=exynos5422-odroidxu3.dtb\0" \
+ "board=odroid\0" \
"board_name=odroidxu3\0" \
"mmcbootdev=0\0" \
"mmcrootdev=0\0" \
-----------------------------------------------------------------------------
On 2022-06-07 19:14, Tom Rini wrote:
On Sat, May 28, 2022 at 03:10:51AM +0300, Gabriel Hojda wrote:
hi,
i've recently tried u-boot 2022.04 (u-boot-v2022.04.tar.bz2) and my
odroid-hc2 didn't boot with uefi (default since Fedora 35) but worked
when i
used exlinux.conf
trying to track down the problem, i've found that in the default
u-boot
environment the "board" and "boardname" variables were "smdk5420" and
not
"odroid" (like before) ... and thus the "fdtfile" variable was
"exynos5422-smdk5420hc1.dtb" and not "exynos5422-odroidhc1.dtb".
continuing i've made a diff between the u-boot-v2021.10.tar.bz2 and
u-boot-v2022.04.tar.bz2 ... and long story short, i've found the
culprit in
commit f76750d1 "Convert CONFIG_CONS_INDEX et al to Kconfig" :
Thanks for the report. Can you please try updating
include/configs/odroid_xu3.h to override "board" in
CONFIG_EXTRA_ENV_SETTINGS and see if the auto-detection works as
expected? We can't change CONFIG_SYS_BOARD as that would then change
wht we look for in board/samsung/ to build.
