From: Ezequiel Garcia <ezequiel@collabora.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Cannot boot mx6qsabred with 2019.07-rc2
Date: Wed, 22 May 2019 15:39:59 -0300 [thread overview]
Message-ID: <151abcf04abd4268076476b5fdfffc06aae595f3.camel@collabora.com> (raw)
In-Reply-To: <20190522151504.GU22232@bill-the-cat>
On Wed, 2019-05-22 at 11:15 -0400, Tom Rini wrote:
> On Wed, May 22, 2019 at 11:23:11AM -0300, Fabio Estevam wrote:
> > On Tue, May 21, 2019 at 11:34 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > > As came up in another thread, CONFIG_MMC_TINY may be more widely useable
> > > and should help with space.
> >
> > How it can be used exactly?
> >
> > I tried it like this:
> >
> > --- a/configs/mx6sabresd_defconfig
> > +++ b/configs/mx6sabresd_defconfig
> > @@ -6,7 +6,6 @@ CONFIG_SPL_LIBCOMMON_SUPPORT=y
> > CONFIG_SPL_LIBGENERIC_SUPPORT=y
> > CONFIG_SYS_MALLOC_F_LEN=0x4000
> > CONFIG_TARGET_MX6SABRESD=y
> > -CONFIG_SPL_MMC_SUPPORT=y
> > CONFIG_SPL_SERIAL_SUPPORT=y
> > CONFIG_NR_DRAM_BANKS=1
> > CONFIG_SPL=y
> > @@ -100,3 +99,4 @@ CONFIG_USB_HOST_ETHER=y
> > CONFIG_USB_ETHER_ASIX=y
> > CONFIG_DM_VIDEO=y
> > CONFIG_VIDEO_IPUV3=y
> > +CONFIG_SPL_MMC_TINY=y
> >
> > , but the board does not boot:
> >
> > U-Boot SPL 2019.07-rc2-00164-ge1a2ed7180-dirty (May 22 2019 - 11:19:41 -0300)
> > SPL: Unsupported Boot Device!
> > SPL: failed to boot from all boot devices
> > ### ERROR ### Please RESET the board ###
>
> Yes, I was hoping to get Marek or Ezequiel to speak up a bit more on how
> to configure / use it, in the other thread.
>
I was planning to look at this, and planned to start with a Wandboard I just happen
to have on my desk.
next prev parent reply other threads:[~2019-05-22 18:39 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
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 [this message]
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=151abcf04abd4268076476b5fdfffc06aae595f3.camel@collabora.com \
--to=ezequiel@collabora.com \
--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