From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] regarding RAM Test
Date: Mon, 2 Dec 2013 10:58:01 -0800 [thread overview]
Message-ID: <529CD839.8000604@freescale.com> (raw)
In-Reply-To: <CAAT48imx1H1BogNA3wbKEk=RuGsdMskP8pBb6tSkyH=i0y0ELg@mail.gmail.com>
On 12/02/2013 10:20 AM, Beagle Board wrote:
> Hi all,
>
> I wanted to perform a RAM test in u-boot for my DM8148 board. I've used the
> "*mtest*" command present in u-boot.
> But its taking ages and it looks like a never ending test.
>
> So guys can anyone point me a way to test maximum RAM memory.
> Here why i'm asking maximum is if I try it from kernel level then some
> amount of RAM will be used up by kernel as well as other applications.
>
> Any thoughts in this regard will be of great help.
>
Just my 2 cents.
Memory testing has two targets. One is to confirm hardware connection.
For this, we have walking 1 test, address test, etc. You can catch
cross-talk, or other "hard" issues. I use POST memory test for this purpose.
The other target is to confirm timing configuration. I found memory test
algorithm is not helpful for this one. I never found any error with
software testing when there is a timing issue. My solution is to rely on
ECC detection and run some memory extensive tests and check ECC status.
The tests I use includes booting Linux, run lmbench, run md5sum on
ramdisk with know files filled with random data and checksum.
Hope this helps.
York
prev parent reply other threads:[~2013-12-02 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 18:20 [U-Boot] regarding RAM Test Beagle Board
2013-12-02 18:58 ` York Sun [this message]
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=529CD839.8000604@freescale.com \
--to=yorksun@freescale.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.