Skip to contentSkip to conversation

udoo_spl: Initialize the eSDHC controller in SPL

PATCH In review Fabio Estevam 3 participants 21 messages Dec 18, 2021 – Jan 9, 2022

Subsystems (3)
lore
Share & tools
lore

Fabio Estevam

author reviewer
#0 lore raw

PATCH 1/6 udoo_spl: Initialize the eSDHC controller in SPL

Currently, imx6q udoo board fails to boot like this:

U-Boot SPL 2022.01-rc3-00061-g95ca715adad3 (Dec 18 2021 - 18:04:40 -0300) Trying to boot from MMC1

The reason is that the eSDHC controller is not initialized in SPL.

Initialize the eSDHC controller in SPL via C code as DM is not used in SPL.

---
 board/udoo/udoo_spl.c | 35 +++++++++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
board/udoo/udoo_spl.c +35 -0
index d9afbbb74198..754bd9dfe21e 100644
@@ -254,4 +254,39 @@ void board_init_f(ulong dummy)
 	/* DDR initialization */
 	spl_dram_init();
 }
+
+#define USDHC3_CD_GPIO		IMX_GPIO_NR(7, 0)
+
+#define USDHC_PAD_CTRL (PAD_CTL_PUS_47K_UP |			\
+	PAD_CTL_SPEED_LOW | PAD_CTL_DSE_80ohm |		\
+	PAD_CTL_SRE_FAST  | PAD_CTL_HYS)
+
+static struct fsl_esdhc_cfg usdhc_cfg[2] = {
+	{USDHC3_BASE_ADDR},
+};
+
+static const iomux_v3_cfg_t usdhc3_pads[] = {
+	IOMUX_PADS(PAD_SD3_CLK__SD3_CLK    | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+	IOMUX_PADS(PAD_SD3_CMD__SD3_CMD    | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+	IOMUX_PADS(PAD_SD3_DAT0__SD3_DATA0 | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+	IOMUX_PADS(PAD_SD3_DAT1__SD3_DATA1 | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+	IOMUX_PADS(PAD_SD3_DAT2__SD3_DATA2 | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+	IOMUX_PADS(PAD_SD3_DAT3__SD3_DATA3 | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+	IOMUX_PADS(PAD_SD3_DAT5__GPIO7_IO00  | MUX_PAD_CTRL(NO_PAD_CTRL)),
+};
+
+int board_mmc_getcd(struct mmc *mmc)
+{
+	return !gpio_get_value(USDHC3_CD_GPIO);
+}
+
+int board_mmc_init(struct bd_info *bis)
+{
+	SETUP_IOMUX_PADS(usdhc3_pads);
+	usdhc_cfg[0].sdhc_clk = mxc_get_clock(MXC_ESDHC3_CLK);
+	usdhc_cfg[0].max_bus_width = 4;
+	gpio_direction_input(USDHC3_CD_GPIO);
+
+	return fsl_esdhc_initialize(bis, &usdhc_cfg[0]);
+}
 #endif
Signature · 1 line
2.25.1
author reviewer
#1 lore raw

PATCH 2/6 ARM: dts: imx6qdl-udoo: Properly describe the SD card detect

GPIO7_IO00 is used as SD card detect.

Properly describe this in the devicetree.

---
 arch/arm/dts/imx6qdl-udoo.dtsi | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
arch/arm/dts/imx6qdl-udoo.dtsi +3 -2
index d07d8f83456d..2d0d102661bd 100644
@@ -4,7 +4,7 @@
  *
  * Author: Fabio Estevam <[email protected]>
  */
-
+#include <dt-bindings/gpio/gpio.h>
 / {
 	aliases {
 		backlight = &backlight;
@@ -226,6 +226,7 @@
 				MX6QDL_PAD_SD3_DAT1__SD3_DATA1		0x17059
 				MX6QDL_PAD_SD3_DAT2__SD3_DATA2		0x17059
 				MX6QDL_PAD_SD3_DAT3__SD3_DATA3		0x17059
+				MX6QDL_PAD_SD3_DAT5__GPIO7_IO00		0x1b0b0
 			>;
 		};
 
@@ -304,7 +305,7 @@
 &usdhc3 {
 	pinctrl-names = "default";
 	pinctrl-0 = <&pinctrl_usdhc3>;
-	non-removable;
+	cd-gpios = <&gpio7 0 GPIO_ACTIVE_LOW>;
 	status = "okay";
 };
 
Signature · 1 line
2.25.1
#2 lore raw

Re: [PATCH 2/6] ARM: dts: imx6qdl-udoo: Properly describe the SD card detect

Quoted 3 lines

GPIO7_IO00 is used as SD card detect.

Properly describe this in the devicetree.

Has this also been sent upstream for the Linux kernel dt?

Quoted 38 lines
---
 arch/arm/dts/imx6qdl-udoo.dtsi | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
arch/arm/dts/imx6qdl-udoo.dtsi +3 -3
index d07d8f83456d..2d0d102661bd 100644
@@ -4,7 +4,7 @@
  *
  * Author: Fabio Estevam <[email protected]>
  */
-
+#include <dt-bindings/gpio/gpio.h>
 / {
        aliases {
                backlight = &backlight;
@@ -226,6 +226,7 @@
                                MX6QDL_PAD_SD3_DAT1__SD3_DATA1          0x17059
                                MX6QDL_PAD_SD3_DAT2__SD3_DATA2          0x17059
                                MX6QDL_PAD_SD3_DAT3__SD3_DATA3          0x17059
+                               MX6QDL_PAD_SD3_DAT5__GPIO7_IO00         0x1b0b0
                        >;
                };
 
@@ -304,7 +305,7 @@
 &usdhc3 {
        pinctrl-names = "default";
        pinctrl-0 = <&pinctrl_usdhc3>;
-       non-removable;
+       cd-gpios = <&gpio7 0 GPIO_ACTIVE_LOW>;
        status = "okay";
 };
 
--

2.25.1

author reviewer
#5 lore raw

PATCH 3/6 udoo: Call gpio_request()

In reply to Fabio Estevam

Calling gpio_request() prior to its usage is now mandatory.

This fixes the following GPIO errors:

U-Boot SPL 2022.01-rc3-00067-g7a5be871c0ec (Dec 18 2021 - 17:45:07 -0300) Trying to boot from MMC1

U-Boot 2022.01-rc3-00067-g7a5be871c0ec (Dec 18 2021 - 17:45:07 -0300)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz                                       
Reset cause: WDOG                                                               
Model: Udoo i.MX6 Quad Board                                                    
Board: Udoo Quad                                                                
DRAM:  1 GiB                                                                    
MMC:   FSL_SDHC: 2                                                              
Loading Environment from MMC... OK                                              
In:    serial                                                                   
Out:   serial                                                                   
Err:   serial                                                                   

gpio@20a0000: set_dir_flags: error: gpio GPIO2_31 not reserved gpio@20a4000: set_dir_flags: error: gpio GPIO3_23 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_24 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_25 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_27 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_28 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_29 not reserved gpio@20a4000: set_value: error: gpio GPIO3_23 not reserved
Net: Could not get PHY for FEC0: addr -2
No ethernet found.

---
 board/udoo/udoo.c | 8 ++++++++
 1 file changed, 8 insertions(+)
board/udoo/udoo.c +8 -0
index 5c49388cbfbe..9e0365615d6d 100644
@@ -90,6 +90,14 @@ int mx6_rgmii_rework(struct phy_device *phydev)
 
 static void setup_iomux_enet(void)
 {
+	gpio_request(IMX_GPIO_NR(2, 31), "eth_power");
+	gpio_request(IMX_GPIO_NR(3, 23), "eth_phy_reset");
+	gpio_request(IMX_GPIO_NR(6, 24), "strap1");
+	gpio_request(IMX_GPIO_NR(6, 25), "strap2");
+	gpio_request(IMX_GPIO_NR(6, 27), "strap3");
+	gpio_request(IMX_GPIO_NR(6, 28), "strap4");
+	gpio_request(IMX_GPIO_NR(6, 29), "strap5");
+
 	gpio_direction_output(IMX_GPIO_NR(2, 31), 1); /* Power supply on */
 
 	gpio_direction_output(IMX_GPIO_NR(3, 23), 0); /* assert PHY rst */
Signature · 1 line
2.25.1
Reviewed-by on v1 3/6
#6 lore raw

Re: [PATCH 3/6] udoo: Call gpio_request()

Quoted 32 lines · Fabio Estevam

Calling gpio_request() prior to its usage is now mandatory.

This fixes the following GPIO errors:

U-Boot SPL 2022.01-rc3-00067-g7a5be871c0ec (Dec 18 2021 - 17:45:07 -0300) Trying to boot from MMC1

U-Boot 2022.01-rc3-00067-g7a5be871c0ec (Dec 18 2021 - 17:45:07 -0300)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: WDOG
Model: Udoo i.MX6 Quad Board
Board: Udoo Quad
DRAM:  1 GiB
MMC:   FSL_SDHC: 2
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial

gpio@20a0000: set_dir_flags: error: gpio GPIO2_31 not reserved gpio@20a4000: set_dir_flags: error: gpio GPIO3_23 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_24 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_25 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_27 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_28 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_29 not reserved gpio@20a4000: set_value: error: gpio GPIO3_23 not reserved
Net: Could not get PHY for FEC0: addr -2
No ethernet found.

Quoted 1 line
Quoted 26 lines
---
 board/udoo/udoo.c | 8 ++++++++
 1 file changed, 8 insertions(+)
board/udoo/udoo.c +8 -1
index 5c49388cbfbe..9e0365615d6d 100644
@@ -90,6 +90,14 @@ int mx6_rgmii_rework(struct phy_device *phydev)
 
 static void setup_iomux_enet(void)
 {
+       gpio_request(IMX_GPIO_NR(2, 31), "eth_power");
+       gpio_request(IMX_GPIO_NR(3, 23), "eth_phy_reset");
+       gpio_request(IMX_GPIO_NR(6, 24), "strap1");
+       gpio_request(IMX_GPIO_NR(6, 25), "strap2");
+       gpio_request(IMX_GPIO_NR(6, 27), "strap3");
+       gpio_request(IMX_GPIO_NR(6, 28), "strap4");
+       gpio_request(IMX_GPIO_NR(6, 29), "strap5");
+
        gpio_direction_output(IMX_GPIO_NR(2, 31), 1); /* Power supply on */
 
        gpio_direction_output(IMX_GPIO_NR(3, 23), 0); /* assert PHY rst */
--

2.25.1

#7 lore raw

Re: [PATCH 3/6] udoo: Call gpio_request()

In reply to Fabio Estevam
Quoted 31 lines · Fabio Estevam

Calling gpio_request() prior to its usage is now mandatory.

This fixes the following GPIO errors:

U-Boot SPL 2022.01-rc3-00067-g7a5be871c0ec (Dec 18 2021 - 17:45:07 -0300) Trying to boot from MMC1

U-Boot 2022.01-rc3-00067-g7a5be871c0ec (Dec 18 2021 - 17:45:07 -0300)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz                                       
Reset cause: WDOG                                                               
Model: Udoo i.MX6 Quad Board                                                    
Board: Udoo Quad                                                                
DRAM:  1 GiB                                                                    
MMC:   FSL_SDHC: 2                                                              
Loading Environment from MMC... OK                                              
In:    serial                                                                   
Out:   serial                                                                   
Err:   serial                                                                   

gpio@20a0000: set_dir_flags: error: gpio GPIO2_31 not reserved gpio@20a4000: set_dir_flags: error: gpio GPIO3_23 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_24 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_25 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_27 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_28 not reserved gpio@20b0000: set_dir_flags: error: gpio GPIO6_29 not reserved gpio@20a4000: set_value: error: gpio GPIO3_23 not reserved
Net: Could not get PHY for FEC0: addr -2
No ethernet found.

Quoted 2 lines

Applied to u-boot/master, thanks!

Signature · 1 line
Tom
author reviewer
#8 lore raw

PATCH 4/6 udoo: Adjust the SD card device numbering

In reply to Fabio Estevam

After the conversion to DM the SD card shows up as 'mmc 2' device.

Adjust the 'mmcdev' and the distro command 'func' accordingly.

---
 configs/udoo_defconfig | 1 +
 include/configs/udoo.h | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)
configs/udoo_defconfig +1 -0
index 8e1bba112041..284ea0588465 100644
@@ -35,6 +35,7 @@ CONFIG_OF_CONTROL=y
 CONFIG_ENV_OVERWRITE=y
 CONFIG_ENV_IS_IN_MMC=y
 CONFIG_SYS_RELOC_GD_ENV_ADDR=y
+CONFIG_SYS_MMC_ENV_DEV=2
 CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG=y
 CONFIG_DM=y
 CONFIG_BOUNCE_BUFFER=y
include/configs/udoo.h +2 -2
index fe6ea68dd461..4bddc0eca30e 100644
@@ -28,7 +28,7 @@
 	"fdt_addr=0x18000000\0" \
 	"fdt_addr_r=0x18000000\0" \
 	"ip_dyn=yes\0" \
-	"mmcdev=0\0" \
+	"mmcdev=2\0" \
 	"mmcrootfstype=ext4\0" \
 	"findfdt="\
 		"if test ${board_rev} = MX6Q; then " \
@@ -44,7 +44,7 @@
 	BOOTENV
 
 #define BOOT_TARGET_DEVICES(func) \
-	func(MMC, mmc, 0) \
+	func(MMC, mmc, 2) \
 	func(SATA, sata, 0) \
 	func(DHCP, dhcp, na)
 
Signature · 1 line
2.25.1
Reviewed-by on v1 4/6
#9 lore raw

Re: [PATCH 4/6] udoo: Adjust the SD card device numbering

Quoted 7 lines · Fabio Estevam

After the conversion to DM the SD card shows up as 'mmc 2' device.

Adjust the 'mmcdev' and the distro command 'func' accordingly.

Quoted 42 lines
---
 configs/udoo_defconfig | 1 +
 include/configs/udoo.h | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)
configs/udoo_defconfig +1 -0
index 8e1bba112041..284ea0588465 100644
@@ -35,6 +35,7 @@ CONFIG_OF_CONTROL=y
 CONFIG_ENV_OVERWRITE=y
 CONFIG_ENV_IS_IN_MMC=y
 CONFIG_SYS_RELOC_GD_ENV_ADDR=y
+CONFIG_SYS_MMC_ENV_DEV=2
 CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG=y
 CONFIG_DM=y
 CONFIG_BOUNCE_BUFFER=y
include/configs/udoo.h +2 -3
index fe6ea68dd461..4bddc0eca30e 100644
@@ -28,7 +28,7 @@
        "fdt_addr=0x18000000\0" \
        "fdt_addr_r=0x18000000\0" \
        "ip_dyn=yes\0" \
-       "mmcdev=0\0" \
+       "mmcdev=2\0" \
        "mmcrootfstype=ext4\0" \
        "findfdt="\
                "if test ${board_rev} = MX6Q; then " \
@@ -44,7 +44,7 @@
        BOOTENV
 
 #define BOOT_TARGET_DEVICES(func) \
-       func(MMC, mmc, 0) \
+       func(MMC, mmc, 2) \
        func(SATA, sata, 0) \
        func(DHCP, dhcp, na)
 
--

2.25.1

author reviewer
#11 lore raw

PATCH 5/6 udoo: Increase CONFIG_ENV_OFFSET

In reply to Fabio Estevam

Increase CONFIG_ENV_OFFSET to avoid the environment region to overlap with U-Boot proper.

---
 configs/udoo_defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
configs/udoo_defconfig +1 -1
index 284ea0588465..ab2b2ee67550 100644
@@ -7,7 +7,7 @@ CONFIG_SPL_LIBCOMMON_SUPPORT=y
 CONFIG_SPL_LIBGENERIC_SUPPORT=y
 CONFIG_NR_DRAM_BANKS=1
 CONFIG_ENV_SIZE=0x2000
-CONFIG_ENV_OFFSET=0x60000
+CONFIG_ENV_OFFSET=0xC0000
 CONFIG_MX6QDL=y
 CONFIG_TARGET_UDOO=y
 CONFIG_DM_GPIO=y
Signature · 1 line
2.25.1
Reviewed-by on v1 5/6
#12 lore raw

Re: [PATCH 5/6] udoo: Increase CONFIG_ENV_OFFSET

Quoted 5 lines · Fabio Estevam

Increase CONFIG_ENV_OFFSET to avoid the environment region to overlap with U-Boot proper.

Quoted 20 lines
---
 configs/udoo_defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
configs/udoo_defconfig +1 -2
index 284ea0588465..ab2b2ee67550 100644
@@ -7,7 +7,7 @@ CONFIG_SPL_LIBCOMMON_SUPPORT=y
 CONFIG_SPL_LIBGENERIC_SUPPORT=y
 CONFIG_NR_DRAM_BANKS=1
 CONFIG_ENV_SIZE=0x2000
-CONFIG_ENV_OFFSET=0x60000
+CONFIG_ENV_OFFSET=0xC0000
 CONFIG_MX6QDL=y
 CONFIG_TARGET_UDOO=y
 CONFIG_DM_GPIO=y
--

2.25.1

author reviewer
#14 lore raw

PATCH 6/6 udoo: Select CMD_DM

In reply to Fabio Estevam

CMD_DM is useful for showing the whole DM tree.

Enable it via "imply CMD_DM".

---
 arch/arm/mach-imx/mx6/Kconfig | 1 +
 1 file changed, 1 insertion(+)
arch/arm/mach-imx/mx6/Kconfig +1 -0
index 62de942a32aa..98df4d4e4281 100644
@@ -588,6 +588,7 @@ config TARGET_UDOO
 	depends on MX6QDL
 	select BOARD_LATE_INIT
 	select SUPPORT_SPL
+	imply CMD_DM
 
 config TARGET_UDOO_NEO
 	bool "UDOO Neo"
Signature · 1 line
2.25.1
Reviewed-by on v1 6/6
#15 lore raw

Re: [PATCH 6/6] udoo: Select CMD_DM

Quoted 6 lines · Fabio Estevam

CMD_DM is useful for showing the whole DM tree.

Enable it via "imply CMD_DM".

Quoted 19 lines
---
 arch/arm/mach-imx/mx6/Kconfig | 1 +
 1 file changed, 1 insertion(+)
arch/arm/mach-imx/mx6/Kconfig +1 -1
index 62de942a32aa..98df4d4e4281 100644
@@ -588,6 +588,7 @@ config TARGET_UDOO
        depends on MX6QDL
        select BOARD_LATE_INIT
        select SUPPORT_SPL
+       imply CMD_DM
 
 config TARGET_UDOO_NEO
        bool "UDOO Neo"
--

2.25.1

Reviewed-by on v1 1/6
#17 lore raw
In reply to Fabio Estevam
Quoted 45 lines · Fabio Estevam

Currently, imx6q udoo board fails to boot like this:

U-Boot SPL 2022.01-rc3-00061-g95ca715adad3 (Dec 18 2021 - 18:04:40 -0300) Trying to boot from MMC1

The reason is that the eSDHC controller is not initialized in SPL.

Initialize the eSDHC controller in SPL via C code as DM is not used in SPL.

---
 board/udoo/udoo_spl.c | 35 +++++++++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
board/udoo/udoo_spl.c +21 -0
index d9afbbb74198..754bd9dfe21e 100644
@@ -254,4 +254,39 @@ void board_init_f(ulong dummy)
        /* DDR initialization */
        spl_dram_init();
 }
+
+#define USDHC3_CD_GPIO         IMX_GPIO_NR(7, 0)
+
+#define USDHC_PAD_CTRL (PAD_CTL_PUS_47K_UP |                   \
+       PAD_CTL_SPEED_LOW | PAD_CTL_DSE_80ohm |         \
+       PAD_CTL_SRE_FAST  | PAD_CTL_HYS)
+
+static struct fsl_esdhc_cfg usdhc_cfg[2] = {
+       {USDHC3_BASE_ADDR},
+};
+
+static const iomux_v3_cfg_t usdhc3_pads[] = {
+       IOMUX_PADS(PAD_SD3_CLK__SD3_CLK    | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+       IOMUX_PADS(PAD_SD3_CMD__SD3_CMD    | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+       IOMUX_PADS(PAD_SD3_DAT0__SD3_DATA0 | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+       IOMUX_PADS(PAD_SD3_DAT1__SD3_DATA1 | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+       IOMUX_PADS(PAD_SD3_DAT2__SD3_DATA2 | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+       IOMUX_PADS(PAD_SD3_DAT3__SD3_DATA3 | MUX_PAD_CTRL(USDHC_PAD_CTRL)),
+       IOMUX_PADS(PAD_SD3_DAT5__GPIO7_IO00  | MUX_PAD_CTRL(NO_PAD_CTRL)),
+};
+

board/udoo/udoo_spl.c void board_init_f(ulong dummy) · line 287

Quoted 10 lines
board/udoo/udoo_spl.c +10 -0
+int board_mmc_getcd(struct mmc *mmc)
+{
+       return !gpio_get_value(USDHC3_CD_GPIO);
+}
+
+int board_mmc_init(struct bd_info *bis)
+{
+       SETUP_IOMUX_PADS(usdhc3_pads);
+       usdhc_cfg[0].sdhc_clk = mxc_get_clock(MXC_ESDHC3_CLK);
+       usdhc_cfg[0].max_bus_width = 4;

Shouldn't there be a gpio_request here before you set direction like in your first patch?

board/udoo/udoo_spl.c void board_init_f(ulong dummy) · line 292

Quoted 5 lines
board/udoo/udoo_spl.c +4 -0
+       gpio_direction_input(USDHC3_CD_GPIO);
+
+       return fsl_esdhc_initialize(bis, &usdhc_cfg[0]);
+}
 #endif
author reviewer
#19 lore raw

Hi Tom,

Quoted 10 lines · Fabio Estevam

Hi Tom/Stefano,

Quoted 1 line · Peter Robinson

Please consider this series and Peter's series on udoo_neo for 2022.01.

They make udoo and udoo_neo functional in U-Boot again.

I saw you picked the udoo_neo series.

Could you please pick this one too for 2022.01?

Thanks

#20 lore raw
In reply to Fabio Estevam
Quoted 5 lines · Fabio Estevam

Currently, imx6q udoo board fails to boot like this:

U-Boot SPL 2022.01-rc3-00061-g95ca715adad3 (Dec 18 2021 - 18:04:40 -0300) Trying to boot from MMC1

Quoted 7 lines

The reason is that the eSDHC controller is not initialized in SPL.

Initialize the eSDHC controller in SPL via C code as DM is not used in SPL.

Applied to u-boot/master, thanks!

Signature · 1 line
Tom