diff mbox series

[v1,1/2] dm: exynos: Correct CONFIG_SYS_BOARD setting for Odroid XU3 boards

Message ID 20240626151522.83561-1-linux.amoon@gmail.com
State Accepted
Commit dd6fff3d83ed13da811a8cbabb876b912e505a7a
Delegated to: Minkyu Kang
Headers show
Series [v1,1/2] dm: exynos: Correct CONFIG_SYS_BOARD setting for Odroid XU3 boards | expand

Commit Message

Anand Moon June 26, 2024, 3:15 p.m. UTC 
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.amoon@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
---
 board/samsung/smdk5420/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


base-commit: c53b344475734d0d29f522b7b1d80c5b8204442d

Comments

Sam Protsenko June 26, 2024, 3:37 p.m. UTC | #1 
On Wed, Jun 26, 2024 at 10:15 AM Anand Moon <linux.amoon@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.amoon@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.protsenko@linaro.org>

>  board/samsung/smdk5420/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/board/samsung/smdk5420/Kconfig b/board/samsung/smdk5420/Kconfig
> index a9d62fffa5..37d6bbbed1 100644
> --- a/board/samsung/smdk5420/Kconfig
> +++ b/board/samsung/smdk5420/Kconfig
> @@ -1,7 +1,7 @@
>  if TARGET_ODROID_XU3
>
>  config SYS_BOARD
> -       default "smdk5420"
> +       default "odroid"
>
>  config SYS_VENDOR
>         default "samsung"
>
> base-commit: c53b344475734d0d29f522b7b1d80c5b8204442d
> --
> 2.44.0
>
Anand Moon July 13, 2024, 7:51 a.m. UTC | #2 
Hi All,

On Wed, 26 Jun 2024 at 21:07, Sam Protsenko <semen.protsenko@linaro.org> wrote:
>
> On Wed, Jun 26, 2024 at 10:15 AM Anand Moon <linux.amoon@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.amoon@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.protsenko@linaro.org>
>
Thanks

Gentle ping?

Thanks
-Anand
Minkyu Kang July 17, 2024, 2:23 a.m. UTC | #3 
Hi,


2024년 7월 13일 (토) 16:51, Anand Moon <linux.amoon@gmail.com>님이 작성:

> Hi All,
>
> On Wed, 26 Jun 2024 at 21:07, Sam Protsenko <semen.protsenko@linaro.org>
> wrote:
> >
> > On Wed, Jun 26, 2024 at 10:15 AM Anand Moon <linux.amoon@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.amoon@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.protsenko@linaro.org>
> >
> Thanks
>
> Gentle ping?
>
> Thanks
> -Anand


applied to u-boot-samsung.

Thanks.
Minkyu Kang.
diff mbox series

Patch

diff --git a/board/samsung/smdk5420/Kconfig b/board/samsung/smdk5420/Kconfig
index a9d62fffa5..37d6bbbed1 100644
--- a/board/samsung/smdk5420/Kconfig
+++ b/board/samsung/smdk5420/Kconfig
@@ -1,7 +1,7 @@ 
 if TARGET_ODROID_XU3
 
 config SYS_BOARD
-	default "smdk5420"
+	default "odroid"
 
 config SYS_VENDOR
 	default "samsung"