From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Cannot boot mx6qsabred with 2019.07-rc2
Date: Fri, 17 May 2019 14:57:50 +0200 [thread overview]
Message-ID: <20190517145750.1973dc4c@jawa> (raw)
In-Reply-To: <CAOMZO5BMzNvoQU89jmxBK-Kot1ofd=98VkuXD8yApj6+efubtA@mail.gmail.com>
On Fri, 17 May 2019 09:39:31 -0300
Fabio Estevam <festevam@gmail.com> wrote:
> On Thu, May 16, 2019 at 11:29 PM Peng Fan <peng.fan@nxp.com> wrote:
>
> > You could enable DEBUG in SPL, and disable SPL_SDP because of size
> > will exceeds. Then see what happends.
>
> Even without DEBUG enabled we get useful error messages:
>
> U-Boot SPL 2019.07-rc2 (May 17 2019 - 09:30:33 -0300)
> Trying to boot from MMC1
> spl: could not find mmc device 0. error: -19
I had similar issue on imx53 (hsc). The problem was with not properly
set GPIO pin by DM/DTS in SPL. The GPIO was responsible for eMMC card
detect, so the SPL code after checking this got the impression that the
card is missing -> hence the -19 error.
Interesting commit: SHA1: 7a0425dd969c44e6afb6936bf8205c8770e9dea9
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
>
> This means that
> err = uclass_get_device(UCLASS_MMC, mmc_dev, &dev); fails inside
> common/spl/spl_mmc.c
>
> Why does this happen?
>
> About the size difference:
>
> Original defconfig generates an SPL of 76800 bytes
> With CONFIG_SPL_DM=y removed the SPL size goes to 68608 bytes.
>
> > I have no idea, then. My board is REV C4, chip 1.5
>
> Mine is rev C2 with i.MX6Q rev1.2
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190517/d8dfc783/attachment.sig>
next prev parent reply other threads:[~2019-05-17 12:57 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 17:32 [U-Boot] Cannot boot mx6qsabred with 2019.07-rc2 Fabio Estevam
2019-05-16 17:37 ` Jagan Teki
2019-05-16 18:23 ` Fabio Estevam
2019-05-16 19:40 ` Fabio Estevam
2019-05-16 21:49 ` Lukasz Majewski
2019-05-17 2:21 ` Fabio Estevam
2019-05-17 2:17 ` Peng Fan
2019-05-17 2:22 ` Fabio Estevam
2019-05-17 2:29 ` Peng Fan
2019-05-17 12:39 ` Fabio Estevam
2019-05-17 12:57 ` Lukasz Majewski [this message]
2019-05-20 14:07 ` Fabio Estevam
2019-05-20 14:15 ` Jagan Teki
2019-05-23 16:11 ` Jagan Teki
2019-05-23 16:48 ` Fabio Estevam
2019-05-23 17:07 ` Jagan Teki
2019-05-23 17:09 ` Fabio Estevam
2019-05-23 17:26 ` Schrempf Frieder
2019-05-23 17:45 ` Fabio Estevam
2019-05-23 17:54 ` Marek Vasut
2019-05-23 17:59 ` Fabio Estevam
2019-05-23 18:00 ` Jagan Teki
2019-05-23 18:03 ` Fabio Estevam
2019-05-23 18:28 ` Adam Ford
2019-05-23 18:35 ` Fabio Estevam
2019-05-23 18:37 ` Adam Ford
2019-05-23 22:03 ` Marek Vasut
2019-05-23 22:04 ` Marek Vasut
2019-05-23 22:08 ` Fabio Estevam
2019-05-23 22:11 ` Marek Vasut
2019-05-23 23:14 ` Fabio Estevam
2019-05-27 6:40 ` Schrempf Frieder
2019-05-28 0:01 ` Fabio Estevam
2019-05-31 9:10 ` Shyam Saini
2019-06-03 6:55 ` Schrempf Frieder
2019-05-31 6:04 ` Peng Fan
2019-05-24 17:43 ` Tom Rini
2019-05-24 20:08 ` Simon Goldschmidt
2019-05-30 10:06 ` Peng Fan
2019-05-21 13:23 ` Fabio Estevam
2019-05-22 1:38 ` Peng Fan
2019-05-22 2:34 ` Tom Rini
2019-05-22 5:52 ` Lukasz Majewski
2019-05-22 14:23 ` Fabio Estevam
2019-05-22 15:15 ` Tom Rini
2019-05-22 15:49 ` Marek Vasut
2019-05-22 18:39 ` Ezequiel Garcia
2019-05-23 13:49 ` Fabio Estevam
2019-05-23 13:59 ` Tom Rini
2019-05-23 14:04 ` Marek Vasut
2019-05-23 15:17 ` Tom Rini
2019-05-23 17:52 ` Marek Vasut
2019-05-31 3:21 ` Peng Fan
2019-05-23 14:08 ` Abel Vesa
2019-05-23 14:33 ` Tom Rini
2019-05-23 14:47 ` Michael Nazzareno Trimarchi
2019-05-23 14:50 ` Tom Rini
2019-05-23 17:51 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190517145750.1973dc4c@jawa \
--to=lukma@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox