From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ezequiel Garcia Date: Fri, 24 May 2019 18:31:21 -0300 Subject: [U-Boot] [PATCH v2 1/3] mx6sabresd: Remove CONFIG_SPL_DM to decrease the SPL size In-Reply-To: <20190521133754.29553-1-festevam@gmail.com> References: <20190521133754.29553-1-festevam@gmail.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, 2019-05-21 at 10:37 -0300, Fabio Estevam wrote: > Currently the mx6qsabresd board does not boot: > > 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 ### > > The reason for the boot failure is that that the SPL > size got greater than the 68KB limit (4KB header + 64KB max > size) as explained in include/configs/imx6_spl.h. > > Remove the CONFIG_SPL_DM option, so that the SPL binary could > fit into the allowed size and the board can boot again. > > Signed-off-by: Fabio Estevam > --- > Changes since v1: > - Improve the commit log by explaining that the boot failure > is caused by SPL size overflow > > configs/mx6sabresd_defconfig | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/configs/mx6sabresd_defconfig b/configs/mx6sabresd_defconfig > index d3ed3c4543..5c2d055561 100644 > --- 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 Since we care about the SPL size, is there any reason why we have CONFIG_SPL_FS_EXT4? AFAICS, u-boot.img is not on a filesystem, so why do we need ext2/3/4? Thanks, Eze