public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Kernel hang when replace older uboot with uboot master V2
Date: Tue, 19 Feb 2019 10:37:29 +0100	[thread overview]
Message-ID: <20190219103729.2cba8561@jawa> (raw)
In-Reply-To: <2019021917305692094016@rosinson.com>

On Tue, 19 Feb 2019 17:30:57 +0800
"rosysong at rosinson.com" <rosysong@rosinson.com> wrote:

> Hi all, 
>     And When I turn off the log, its bootlog like this:
> 
> U-Boot 2019.01-00079-g3420a6fc6e-dirty (Feb 19 2019 - 17:19:16 +0800)
> 
> Qualcomm Atheros QCA9561 ver 1 rev 0
> Model: AP152 Reference Board
> DRAM:  128 MiB
> Loading Environment from SPI Flash... SF: Detected w25q128bv with
> page size 256 Bytes, erase size 4 KiB, total 16 MiB, mapped at
> 9f000000 *** Warning - bad CRC, using default environment

Here is the culprit - the on-board (tuned, setup) envs are not
accessible (or read in a wrong way).

Apparently the default envs doesn't have proper root=... setup.

Please check the env related entries in Kconfig.


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190219/51e4e19c/attachment.sig>

  reply	other threads:[~2019-02-19  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  9:30 [U-Boot] Kernel hang when replace older uboot with uboot master V2 rosysong at rosinson.com
2019-02-19  9:37 ` Lukasz Majewski [this message]
2019-02-19  9:45   ` rosysong at rosinson.com
2019-02-19 10:49     ` Lukasz Majewski
2019-02-20  2:16       ` rosysong at rosinson.com
2019-02-19  9:48   ` rosysong at rosinson.com

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=20190219103729.2cba8561@jawa \
    --to=lukma@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox