From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC
Date: Mon, 21 May 2018 15:00:10 -0700 [thread overview]
Message-ID: <87lgccsm8l.fsf@aikidev.net> (raw)
In-Reply-To: <87in7suzho.fsf@aikidev.net>
On 2018-05-12, Vagrant Cascadian wrote:
> On 2018-05-12, Vagrant Cascadian wrote:
>> Booting firefly-rk3288 seems to hang looking for environment:
>>
>> U-Boot 2018.05+dfsg-1 (May 10 2018 - 20:24:57 +0000)
>>
>> Model: Firefly-RK3288
>> DRAM: 2 GiB
>> MMC: dwmmc at ff0c0000: 1, dwmmc at ff0f0000: 0
>> Loading Environment from MMC...
>>
>> And just hangs there.
I tried to bisect this, and got:
commit 04a2ea248f58b3b6216d0cd0a6b8698df8b14355
Author: Jean-Jacques Hiblot <jjhiblot@ti.com>
Date: Thu Sep 21 16:30:08 2017 +0200
mmc: disable UHS modes if Vcc cannot be switched on and off
But it fails in a slightly different way:
U-Boot 2018.01-00026-g04a2ea248f (May 21 2018 - 21:46:18 +0000)
Model: Firefly-RK3288
DRAM: 2 GiB
MMC: dwmmc at ff0c0000: 1, dwmmc at ff0f0000: 0
And just hangs without the "Loading Environment from MMC..."
part...
It is not a trivial revert on top of 2018.05, so I haven't been able to
do that simple test.
CONFIG_ENV_IS_IN_MMC has been enabled since at least:
5dc4dfd2a94 (Tom Rini 2017-08-28 07:16:32 -0400 36) CONFIG_ENV_IS_IN_MMC=y
live well,
vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180521/c730a566/attachment.sig>
next parent reply other threads:[~2018-05-21 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lgcov1qq.fsf@aikidev.net>
[not found] ` <87in7suzho.fsf@aikidev.net>
2018-05-21 22:00 ` Vagrant Cascadian [this message]
2018-06-05 18:57 ` [U-Boot] u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC Vagrant Cascadian
2018-08-14 21:00 ` Vagrant Cascadian
2018-08-14 21:12 ` Vagrant Cascadian
2018-08-14 22:12 ` Vagrant Cascadian
2018-12-19 3:05 ` Simon Glass
2018-12-24 16:14 ` Vagrant Cascadian
2018-12-27 1:00 ` Kever Yang
2018-12-27 14:36 ` Philipp Tomsich
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=87lgccsm8l.fsf@aikidev.net \
--to=vagrant@debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.