public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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: Tue, 14 Aug 2018 15:12:40 -0700	[thread overview]
Message-ID: <87woss8unb.fsf@aikidev.net> (raw)
In-Reply-To: <87zhxo8xf8.fsf@aikidev.net>

On 2018-08-14, Vagrant Cascadian wrote:
>> Also just tried with v2018.09-rc2, same problem.

With some debugging in mmc enabled (#define DEBUG at the top of dw_mmc.c
mmc-uclass.c mmc.c rockchip_dw_mmc.c) and CONFIG_MMC_TRACE=y, it gives a
little more information:

U-Boot SPL 2018.09-rc2+dfsg-1~20180814~6 (Aug 14 2018 - 21:58:09 +0000)
Returning to boot ROM...
mmc_bind: alias ret=0, devnum=1


U-Boot 2018.09-rc2+dfsg-1~20180814~6 (Aug 14 2018 - 21:58:09 +0000)

Model: Firefly-RK3288
DRAM:  2 GiB
mmc_bind: alias ret=0, devnum=1
mmc_bind: alias ret=0, devnum=0
MMC:   dwmmc at ff0c0000: 1, dwmmc at ff0f0000: 0
Loading Environment from MMC... clock is disabled (0Hz)

Buswidth = 0, clock: 0


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/20180814/ab8715ab/attachment.sig>

  reply	other threads:[~2018-08-14 22:12 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   ` [U-Boot] u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC Vagrant Cascadian
2018-06-05 18:57     ` Vagrant Cascadian
2018-08-14 21:00       ` Vagrant Cascadian
2018-08-14 21:12         ` Vagrant Cascadian
2018-08-14 22:12           ` Vagrant Cascadian [this message]
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=87woss8unb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox