public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 13:07:10 -0400	[thread overview]
Message-ID: <1566234430.11007.49.camel@intricatesoftware.com> (raw)
In-Reply-To: <CAMty3ZD56iY8sGyeDaGf1ykqo6Q7jq_R9DJEe4MwPYceuv=wZg@mail.gmail.com>

On Mon, 2019-08-19 at 22:11 +0530, Jagan Teki wrote:
> On Mon, Aug 19, 2019 at 8:42 PM Kurt Miller <lists@intricatesoftware.com> wrote:
> > 
> > 
> > Hi Michael,
> > 
> > On Mon, 2019-08-19 at 16:06 +0200, Michael Nazzareno Trimarchi wrote:
> > > 
> > > It's possible to dump the register after training in mainline uboot?
> > I'm working on getting master to build now. How would I
> > go about dumping the register after training?
> It would be a bit hard, I tried below sequence at the end of
> sdram_init (sorry for direct copy)
> 
>         printf("cic: ctr10: (0x%x - 0x%x)\n", &dram->cic->cic_ctrl0,
> readl(&dram->cic->cic_ctrl0));
>         printf("cic: status0: (0x%x - 0x%x)\n",
> &dram->cic->cic_status0, readl(&dram->cic->cic_status0));
>         printf("grf: ddrc0_con0 (0x%x - 0x%x)\n",
> &dram->grf->ddrc0_con0, readl(&dram->grf->ddrc0_con0));
>         printf("grf: ddrc1_con0 (0x%x - 0x%x)\n",
> &dram->grf->ddrc1_con0, readl(&dram->grf->ddrc1_con0));
>         printf("grf: soc_con0 (0x%x - 0x%x)\n", &dram->grf->soc_con0,
> readl(&dram->grf->soc_con0));
>         printf("pmu: noc_auto_ena (0x%x - 0x%x)\n",
> &dram->pmu->pmu_noc_auto_ena, readl(&dram->pmu->pmu_noc_auto_ena));
>         printf("pmu: bus_idle_req (0x%x - 0x%x)\n",
> &dram->pmu->pmu_bus_idle_req, readl(&dram->pmu->pmu_bus_idle_req));
>         printf("pmu: bus_idle_st (0x%x - 0x%x)\n",
> &dram->pmu->pmu_bus_idle_st, readl(&dram->pmu->pmu_bus_idle_st));
>         printf("pmugrf: os_reg2 (0x%x - 0x%x)\n",
> &dram->pmugrf->os_reg2, readl(&dram->pmugrf->os_reg2));
>         printf("pmugrf: os_reg3 (0x%x - 0x%x)\n",
> &dram->pmugrf->os_reg3, readl(&dram->pmugrf->os_reg3));
>         printf("pmusgrf: soc_con4 (0x%x - 0x%x)\n",
> &dram->pmusgrf->soc_con4, readl(&dram->pmusgrf->soc_con4));

Thank you. I have built mainline with CONFIG_RAM_ROCKCHIP_DEBUG=y
with your printf's above and it outputs the following before freezing:

U-Boot TPL 2019.10-rc2-00016-g81fed78c0a-dirty (Aug 19 2019 - 12:57:39)      
LPDDR4, 50MHz                                                                
BW=32 Col=10 Bk=8 CS0 Row=15 CS=1 Die BW=16 Size=1024MB                      
LPDDR4, 50MHz                                                                
BW=32 Col=10 Bk=8 CS0 Row=15 CS=1 Die BW=16 Size=1024MB
256B stride                             
cic: ctr10: (0xff620000 - 0x14)         
cic: status0: (0xff620010 - 0x101)      
grf: ddrc0_con0 (0xff77e380 - 0x1f81)   
grf: ddrc1_con0 (0xff77e388 - 0x1f81)   
grf: soc_con0 (0xff77e200 - 0x7)
pmu: noc_auto_ena (0xff3100d8 - 0x0)
pmu: bus_idle_req (0xff310060 - 0x0)
pmu: bus_idle_st (0xff310064 - 0x0)
pmugrf: os_reg2 (0xff320308 - 0x32a1f2a1)
pmugrf: os_reg3 (0xff32030c - 0x20000005)
pmusgrf: soc_con4 (0xff33e010 - 0x2600)

Note that 'Size=1024MB' is incorrect. With 'rockchip-linux' TPL
I see 'Size=2048MB'.

Regards,
-Kurt

  reply	other threads:[~2019-08-19 17:07 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
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 [this message]
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=1566234430.11007.49.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox