From: Kurt Miller <lists@intricatesoftware.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Rockpro64_V2.1 2018-07-02 Boot Freeze
Date: Mon, 19 Aug 2019 10:03:57 -0400 [thread overview]
Message-ID: <1566223437.11007.33.camel@intricatesoftware.com> (raw)
In-Reply-To: <a03454bf6f2f4a46@bloch.sibelius.xs4all.nl>
On Mon, 2019-08-19 at 15:31 +0200, Mark Kettenis wrote:
> >
> > From: Jagan Teki <jagan@amarulasolutions.com>
> > Date: Mon, 19 Aug 2019 00:21:40 +0530
> >
> > + Kever
> >
> > On Sun, Aug 18, 2019 at 1:21 AM Kurt Miller <lists@intricatesoftware.com> wrote:
> > >
> > >
> > > 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.
> > Please use mainline, and with doc/README.rockchip instructions.
> This is mainline as of Aug 16. I built the image for Kurt and it the
> same binaries (one for TPL+SPL one for U-Boot+ATF) works fine on my
> board.
>
> >
> > I'm able to boot with mainline tree.
> Sure I can believe that. I believe your board from the same batch as
> mine. I suspect that the DRAM used on Kurt's board may require
> slightly different timings.
>
While my board (2018-07-02) freezes with Aug 16 mainline TPL,
it does boot ok with the rockchip-linux TPL with the following
output which may have some useful info:
DDR Version 1.23 20190709
In
channel 0
CS = 0
MR0=0xB8
MR4=0x1
MR5=0xFF
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0xB8
MR4=0x1
MR5=0xFF
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0xB8
MR4=0x1
MR5=0xFF
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0xB8
MR4=0x1
MR5=0xFF
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
OUT
next prev parent reply other threads:[~2019-08-19 14:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 21:44 [U-Boot] Rockpro64_V2.1 2018-07-02 Boot Freeze Kurt Miller
2019-08-18 18:51 ` Jagan Teki
2019-08-19 13:31 ` Mark Kettenis
2019-08-19 14:03 ` Kurt Miller [this message]
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=1566223437.11007.33.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.