[U-Boot] [PATCH v1 9/9] ARM: Odroid XU3: Modify Odroid XU3 config to boot by default from SD card

Anand Moon linux.amoon at gmail.com
Thu Jul 26 15:28:02 UTC 2018


Hi Lukasz,

On 26 July 2018 at 03:55, Lukasz Majewski <lukma at denx.de> wrote:
> This commit allows by default booting Odroid XU3 from the SD card (when
> e.g. eMMC module is not present).
>
> Signed-off-by: Lukasz Majewski <lukma at denx.de>
>
> ---
>
>  include/configs/odroid_xu3.h | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/include/configs/odroid_xu3.h b/include/configs/odroid_xu3.h
> index f495f6219ba9..818a06515cb2 100644
> --- a/include/configs/odroid_xu3.h
> +++ b/include/configs/odroid_xu3.h
> @@ -94,6 +94,9 @@
>  #undef CONFIG_SYS_BOARD
>  #define CONFIG_SYS_BOARD       "odroid"
>
> +#undef CONFIG_SYS_MMC_ENV_DEV
> +#define CONFIG_SYS_MMC_ENV_DEV         2
> +
>  /* Define new extra env settings, including DFU settings */
>  #undef CONFIG_EXTRA_ENV_SETTINGS
>  #define CONFIG_EXTRA_ENV_SETTINGS \
> @@ -105,8 +108,8 @@
>         "console=" CONFIG_DEFAULT_CONSOLE "\0"\
>         "fdtfile=exynos5422-odroidxu3.dtb\0" \
>         "boardname=odroidxu3\0" \
> -       "mmcbootdev=0\0" \
> -       "mmcrootdev=0\0" \
> +       "mmcbootdev=2\0" \
> +       "mmcrootdev=1\0" \
>         "mmcbootpart=1\0" \
>         "mmcrootpart=2\0" \
>         "dfu_alt_system="CONFIG_DFU_ALT_SYSTEM \
> --
> 2.11.0
>

This changes probably breaks the booting from eMMC on  Odroid-XU4

U-Boot 2018.07-00377-g80df37b417 (Jul 26 2018 - 10:50:16 +0000) for
ODROID-XU3/XU4/HC1

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 2
Loading Environment from MMC... Card did not respond to voltage select!
*** Warning - No block device, using default environment

Failed (-5)
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
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 U-Boot script /boot.scr
3069 bytes read in 6 ms (499 KiB/s)
## Executing script at 50000000
Card did not respond to voltage select!
** Bad device mmc 2 **
Card did not respond to voltage select!
** Bad device mmc 2 **
Card did not respond to voltage select!
** Bad device mmc 2 **
SCRIPT FAILED: continuing...
63776 bytes read in 7 ms (8.7 MiB/s)
Card did not respond to voltage select!
starting USB...
USB0:   USB EHCI 1.00
USB1:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 3 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 1 Ethernet Device(s) found
Waiting for Ethernet connection... done.
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 10.0.0.144 (1021 ms)
*** Warning: no boot file name; using '0A000090.img'
Using r8152#0 device
TFTP from server 0.0.0.0; our IP address is 10.0.0.144; sending
through gateway 10.0.0.1
Filename '0A000090.img'.
Load address: 0x43e00000
Loading: T

Best Regards
-Anand


More information about the U-Boot mailing list