From: "Marek Behún" <kabel@kernel.org>
To: Chris Packham <judge.packham@gmail.com>
Cc: "Chris Packham" <chris.packham@alliedtelesis.co.nz>,
"Stefan Roese" <sr@denx.de>, "Baruch Siach" <baruch@tkos.co.il>,
"Pavol Rohár" <pali@kernel.org>, u-boot <u-boot@lists.denx.de>,
"Mario Six" <mario.six@gdsys.cc>,
"Dennis Gilmore" <dgilmore@redhat.com>,
"Kostya Porotchkin" <kostap@marvell.com>,
"Marek Behún" <marek.behun@nic.cz>
Subject: Re: [PATCH u-boot-marvell] PLEASE TEST ddr: marvell: a38x: fix SPLIT_OUT_MIX state decision
Date: Wed, 5 Jan 2022 10:10:41 +0100 [thread overview]
Message-ID: <20220105101041.600c2f75@thinkpad> (raw)
In-Reply-To: <CAFOYHZBbobi8qLaAAhPO2OYyD0ZMNYuOH_LKbgsHUpnk2p4y5A@mail.gmail.com>
On Wed, 5 Jan 2022 11:10:51 +1300
Chris Packham <judge.packham@gmail.com> wrote:
> Hi Marek,
>
> On Wed, Jan 5, 2022 at 9:28 AM Marek Behún <kabel@kernel.org> wrote:
> >
> > From: Marek Behún <marek.behun@nic.cz>
> >
> > Hello,
> >
> > continuing my last discussion with Chris [1] about this, could you
> > please test this change? (For Chris, mainly on your x530, since last
> > time you said it hanged your board in SPL.)
>
> I still get a hang after "Returning to BootROM (return address
> 0xffff05c4)... " (after the DDR training).
Hi Chris,
would it be possible for me to connect to a computer to which the x530
is connected via UART so that I can debug it? Could you prepare such an
environment? It would also need a mechanism to reset the board remotely
somehow. I prepared a similar remote debugging environment for Marvell
when they were solving some issues for us.
If not, then I guess we will just have to send debugging code and
results back and forth.
Marek
next prev parent reply other threads:[~2022-01-05 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 20:28 [PATCH u-boot-marvell] PLEASE TEST ddr: marvell: a38x: fix SPLIT_OUT_MIX state decision Marek Behún
2022-01-04 22:10 ` Chris Packham
2022-01-05 9:10 ` Marek Behún [this message]
2022-01-05 22:51 ` Chris Packham
2022-01-06 3:04 ` Chris Packham
-- strict thread matches above, loose matches on Subject: below --
2021-02-08 19:12 Marek Behún
2021-02-08 19:15 ` Marek Behun
2021-02-08 20:14 ` Chris Packham
2021-02-08 20:24 ` Marek Behun
2021-06-28 7:20 ` Pali Rohár
2021-06-28 9:21 ` Chris Packham
2021-06-28 9:53 ` Chris Packham
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=20220105101041.600c2f75@thinkpad \
--to=kabel@kernel.org \
--cc=baruch@tkos.co.il \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=dgilmore@redhat.com \
--cc=judge.packham@gmail.com \
--cc=kostap@marvell.com \
--cc=marek.behun@nic.cz \
--cc=mario.six@gdsys.cc \
--cc=pali@kernel.org \
--cc=sr@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;
as well as URLs for NNTP newsgroup(s).