mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: memtest failed for rk3588
Date: Fri, 6 Dec 2024 15:25:01 +0100	[thread overview]
Message-ID: <Z1MJPVfJY7v2vEgL@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvQXh3sQz8exOva9oY-XFUh0ULrSuuAA5fNrCREdw8cxAA@mail.gmail.com>

Hi Alexander,

On Fri, Dec 06, 2024 at 04:10:42PM +0300, Alexander Shiyan wrote:
> Hello all!
> 
> When testing a board with a RK3588 CPU, I get a stable crash on memtest.
> This is the first sample of the board on this CPU and of course it is possible
> that something is really not soldered correctly, but should the
> bootloader crash in this case?
> 
> 
> Testing memory space: 0x0000000100000000 -> 0x00000003ffffffff:
> Starting data line test.
> Check for address bits stuck high.
> Check for address bits stuck low or shorted.
> Starting moving inversions test of RAM:
> Fill with address, compare, fill with inverted address, compare again
>         [##########################################DABT (current EL)
> exception (ESR 0x96000010) at 0x00000003fc000200

Can you access 0x3fc000200 using md/mw?

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2024-12-06 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 13:10 Alexander Shiyan
2024-12-06 14:25 ` Sascha Hauer [this message]
2024-12-10 11:29   ` Alexander Shiyan
2024-12-10 11:47     ` Sascha Hauer
2024-12-11 15:52       ` Alexander Shiyan
2024-12-13 12:15         ` Alexander Shiyan

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=Z1MJPVfJY7v2vEgL@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=eagle.alexander923@gmail.com \
    /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