All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot Boot issue about rk3188
Date: Thu, 21 Sep 2017 16:55:38 +0200	[thread overview]
Message-ID: <10916501.0dBLUKaQFm@diego> (raw)
In-Reply-To: <1506002612-21773-1-git-send-email-andy.yan@rock-chips.com>

Hi Andy,

Am Donnerstag, 21. September 2017, 22:03:32 CEST schrieb Andy Yan:
> Hi Heiko:
> I try to boot the upstream u-boot-rockchip branch  on my rk3188 board
> with(rock_defconfig)
> 
> But I got this error:
> early_init()
> nit_and_scan() returned error -22
> early_init() failed: -22
> ERROR ### Please RESET the board ###
> 
> the current commit head is: 782088d("rockchip: imply ADC and SARADC_ROCKCHIP
> on supported SoCs") Do you ever meet something like this?

that is very strange. When testing Philipp's branch, I was also testing the 
commit you mention to see if anything broke since I last changed u-boot
on my radxa rock. And the above commit started just fine, when starting
from an sd-card.

Not sure from which medium you're starting though. But from what I
remember Pawel got nand working in his rk3066 series, but that is not
yet merged.


Heiko

  reply	other threads:[~2017-09-21 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 14:03 [U-Boot] u-boot Boot issue about rk3188 Andy Yan
2017-09-21 14:55 ` Heiko Stübner [this message]
2017-09-22  0:24   ` Andy Yan
2017-09-22  0:50     ` Andy Yan
2017-09-22  5:56       ` Heiko Stuebner
2017-09-25  9:45         ` Andy Yan
2017-09-25 10:29           ` Heiko Stübner
2017-09-25 11:49             ` Andy Yan
2017-09-25 12:48               ` Heiko Stübner
2017-09-26 11:34             ` Paweł Jarosz
2017-09-27  1:48               ` Andy Yan
2017-09-27  6:55                 ` Paweł Jarosz
2017-09-27  7:46                   ` Andy Yan
2017-09-27  8:38                     ` Paweł Jarosz

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=10916501.0dBLUKaQFm@diego \
    --to=heiko@sntech.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 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.