From: Michael Trimarchi <michael@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Tinker-rk3288 SPL broken with MMC timeout
Date: Sat, 14 Sep 2019 14:17:09 +0200 [thread overview]
Message-ID: <20190914121708.GA1304@panicking> (raw)
In-Reply-To: <CAMty3ZCipUZC9G=jA1aTJCcU9OoHEVAYKdCn6O_Z+QW1fqMc2g@mail.gmail.com>
On Fri, Sep 13, 2019 at 08:11:17AM +0530, Jagan Teki wrote:
> On Thu, Sep 12, 2019 at 8:25 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Sep 12, 2019 at 08:55:24AM +0530, Jagan Teki wrote:
> >
> > > I have seen this even on v2019.07 release, and the only release that
> > > it got working with on v2019.01 (SPL, BROM_RETURN)
> > >
> > > Any idea? here is the log dump.
> > >
> > > U-Boot TPL 2019.10-rc3-00297-g5ba8b12543 (Sep 12 2019 - 08:50:36)
> > > Trying to boot from BOOTROM
> > > Returning to boot ROM...
> > >
> > > U-Boot SPL 2019.10-rc3-00297-g5ba8b12543 (Sep 12 2019 - 08:50:36 +0530)
> > > Trying to boot from MMC1
> > > spl: mmc init failed with error: -110
> > > SPL: failed to boot from all boot devices
> > > ### ERROR ### Please RESET the board ###
> >
> > Time to run 'git bisect' since you know when it worked last at least?
>
> Look hard to bisect, few of commits in between seems SPL size
> blow-out, doesn't boot etc. May be verify with respect boards might
> help.
Well I think that ddr should follow the same rule of rk3399, but still
the mmc is not working
next prev parent reply other threads:[~2019-09-14 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 3:25 [U-Boot] Tinker-rk3288 SPL broken with MMC timeout Jagan Teki
2019-09-12 14:55 ` Tom Rini
2019-09-13 2:41 ` Jagan Teki
2019-09-13 15:44 ` Tom Rini
2019-09-13 18:08 ` Michael Nazzareno Trimarchi
2019-09-14 12:17 ` Michael Trimarchi [this message]
2019-09-14 13:26 ` Michael Nazzareno Trimarchi
2019-09-16 8:24 ` Kever Yang
2019-09-16 8:25 ` Jagan Teki
2019-09-16 11:11 ` Michael Nazzareno Trimarchi
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=20190914121708.GA1304@panicking \
--to=michael@amarulasolutions.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