From: Arun Dharankar <ADharankar@ATTBI.Com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problem: SDRAM configuration and refresh
Date: Tue, 11 Jun 2002 23:03:04 -0400 [thread overview]
Message-ID: <200206112303.04576.ADharankar@ATTBI.Com> (raw)
In-Reply-To: <20020611192251.WCYS2751.rwcrmhc52.attbi.com@rwcrwbc57>
Greetings!
Thanks to anyone who might have attempted to
help out! The problem turned out to by too low
SDRAM refresh interval.
Best regards,
-Arun.
On Tuesday 11 June 2002 03:22 pm, adharankar@attbi.com wrote:
> Greetings,
>
> I am trying to getup a Scout based board with
> 64MB SDRAM, and could use any recommendations
> to fix this problem:
>
> If I set the refresh-enable bit in the PSDMR,
> the chipselect for flash and other devices
> vanishes: consequently, this startup code
> ends up executing junk. At this point if I try
> to look at the flash from the BDI2000, the
> flash cannot be seen.
>
>
>
> On the other hand, if I initialize the SDRAM
> without setting this refresh-enable bit, ppcboot
> (the code using it) comes up and am able to run
> commands etc. However, the problem now is that
> without the SDRAM refresh we run into memory
> corruption problem (mtest will fail) and a system
> hang.
>
> Its interesting to note that as long as memory
> is accessed frequently (say via mtest), the
> corruption is not see at that address. Also, an
> idle system almost hangs in a very short time,
> whereas an active one with mtest will continue on.
>
>
>
> Best regards,
> -Arun.
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-06-12 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 19:22 Problem: SDRAM configuration and refresh adharankar
2002-06-12 3:03 ` Arun Dharankar [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=200206112303.04576.ADharankar@ATTBI.Com \
--to=adharankar@attbi.com \
--cc=linuxppc-embedded@lists.linuxppc.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).