From: Kurt Miller <lists@intricatesoftware.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Rockpro64_V2.1 2018-07-02 Boot Freeze
Date: Fri, 16 Aug 2019 17:44:46 -0400 [thread overview]
Message-ID: <1565991886.11007.28.camel@intricatesoftware.com> (raw)
Hello,
The Rockpro64_V2.1 2018-07-02 using master code base freezes
with only the following output:
U-Boot TPL 2019.10-rc2-00001-gdf33f86468-dirty (Aug 16 2019 - 22:31:31)
Whereas another board dated 2018-06-06 works and outputs the following:
U-Boot TPL 2019.10-rc2-00001-gdf33f86468-dirty (Aug 16 2019 - 22:31:31)
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2019.10-rc2-00001-gdf33f86468-dirty (Aug 16 2019 - 22:31:31 +0200)
Both board have 4G RAM.
U-Boot was built by Mark Kettenis from master with only the
baud rate changed for both tests. The 2018-07-02 board has different
markings for the CPU and the RAM as follows:
2018-06-06 2018-07-02
CPU: RK3399 RK3399
SBETMF976 1652 SBETNM271 1826
RAM: PS006-075 BT PS052-053 BT
N1YJ 83RL
Please let me know if there is additional information needed to
further diagnose the boot freeze.
Regards,
-Kurt
next reply other threads:[~2019-08-16 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 21:44 Kurt Miller [this message]
2019-08-18 18:51 ` [U-Boot] Rockpro64_V2.1 2018-07-02 Boot Freeze Jagan Teki
2019-08-19 13:31 ` Mark Kettenis
2019-08-19 14:03 ` Kurt Miller
2019-08-19 14:06 ` Michael Nazzareno Trimarchi
2019-08-19 15:12 ` Kurt Miller
2019-08-19 16:41 ` Jagan Teki
2019-08-19 17:07 ` Kurt Miller
2019-08-19 17:56 ` Jagan Teki
2019-08-19 23:32 ` Kurt Miller
2019-08-20 2:46 ` [U-Boot] Rockpro64_V2.1 2018-07-02 Boot Freeze【请注意，邮件由lists.intricate@gmail.com代发】 Kever Yang
2019-08-20 13:57 ` [U-Boot] Rockpro64_V2.1 2018-07-02 Boot Freeze Kurt Miller
2019-08-19 16:38 ` Jagan Teki
2019-08-19 18:04 ` Kurt Miller
2019-08-19 16:14 ` Jagan Teki
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=1565991886.11007.28.camel@intricatesoftware.com \
--to=lists@intricatesoftware.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 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.