linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Atit_Shah" <Atit_Shah@satyam.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: RAM test - How to
Date: Wed, 20 Apr 2005 09:40:03 +0200	[thread overview]
Message-ID: <20050420074008.B7CA2C1784@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 20 Apr 2005 10:22:40 +0530." <D8595042F3765A4285B848A78A2C2ED102774F@bsdmsg002.corp.satyam.ad>

In message <D8595042F3765A4285B848A78A2C2ED102774F@bsdmsg002.corp.satyam.ad> you wrote:
> 
> 	I am using a SDRAM having a port size 64 and size 32MB, and the
> burst length is 4. I want to know how i can test my RAM for burst mode
> operation. I have read in a couple of places that there is no sure RAM
> test but there must be some reasonable test which can be performed to
> atleast be sure that the RAM functions fine under burst mode.

You can probably implement a memory test like this one:

1)  Map a region of physical RAM into two virtual regions:
    one cached and the the other one uncached.
2)  Fill the cached region with a pattern, and flush the cache
2a) Check the uncached region to match the pattern
2b) Check the cached region to match the pattern
3)  Fill the uncached region with a pattern
3a) Check the cached region to match the pattern
3b) Check the uncached region to match the pattern
4)  Change the patterns and go to step 2.

You probably want to do this in your boot loader, though.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
A Freudian slip is when you say one thing but mean your mother.

      reply	other threads:[~2005-04-20  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20  4:52 RAM test - How to Atit_Shah
2005-04-20  7:40 ` Wolfgang Denk [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=20050420074008.B7CA2C1784@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Atit_Shah@satyam.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).