From mboxrd@z Thu Jan  1 00:00:00 1970
From: Fabio Estevam <festevam@gmail.com>
Date: Thu, 16 May 2019 16:40:56 -0300
Subject: [U-Boot] Cannot boot mx6qsabred with 2019.07-rc2
In-Reply-To: <CAOMZO5C-9R1mxEwmxUG3n_DUymXy-S23vU589yzZ=sq63T6+Mg@mail.gmail.com>
References: <CAOMZO5C-9R1mxEwmxUG3n_DUymXy-S23vU589yzZ=sq63T6+Mg@mail.gmail.com>
Message-ID: <CAOMZO5AnScYwFW8Y0EiZJRthHJkdWHfswcbDBVRxqKA35pQ-jA@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Thu, May 16, 2019 at 2:32 PM Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi,
>
> I get the following error when trying to boot mx6q sabresd with 2019.07-rc2:
>
> U-Boot SPL 2019.07-rc2 (May 16 2019 - 14:28:55 -0300)
> Trying to boot from MMC1
> spl: could not find mmc device 0. error: -19
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
>
> I haven't debugged this yet.
>
> Does anyone have any ideas?

SPL is able to load u-boot-dtb.img if I disable CONFIG_SPL_DM:

--- a/configs/mx6sabresd_defconfig
+++ b/configs/mx6sabresd_defconfig
@@ -65,7 +65,6 @@ CONFIG_SPL_MULTI_DTB_FIT=y
 CONFIG_SPL_OF_LIST="imx6dl-sabresd imx6q-sabresd imx6qp-sabresd"
 CONFIG_ENV_IS_IN_MMC=y
 CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG=y
-CONFIG_SPL_DM=y
 CONFIG_USB_FUNCTION_FASTBOOT=y
 CONFIG_FASTBOOT_BUF_ADDR=0x12000000
 CONFIG_FASTBOOT_BUF_SIZE=0x10000000

Do we really want to use DM within SPL?

If we do, does anyone know how to fix it?