From: Pete Popov <ppopov@mvista.com>
To: baitisj@evolution.com
Cc: Linux MIPS mailing list <linux-mips@linux-mips.org>
Subject: Re: Power On Self Test and testing memory
Date: 14 May 2003 15:34:01 -0700 [thread overview]
Message-ID: <1052951641.788.225.camel@zeus.mvista.com> (raw)
In-Reply-To: <20030514152643.A5897@luca.pas.lab>
On Wed, 2003-05-14 at 15:26, Jeff Baitis wrote:
> Hi all:
>
> I implemented memory tests in my bootloader code for the AU1500. I'm trying
> to figure out why Linux boots when loaded into cached KSEG0 (0x 80c0 0000),
> but my memory test FAILS for this same region.
>
> (pretty backwards huh? get linux booting, then write memory tests!)
>
>
> I start by writing 0x5555 5555 to all of uncached memory, reading it back, and
> I write 0xAAAA AAAA to all of uncached memory and read it back.
>
> This works great.
>
> Next, I try to write 0x5555 5555 to cached KSEG0 memory, and it fails at addr
> 0x8000FE50. But Linux boots!
You're not overwriting any of the boot exception vectors, right? What's
the failure exactly and how does the test work?
Pete
> I'm not issuing SYNC commands when writing to cached memory; could this be
> the problem?
>
> We've exhaustively verified the memory burst parameters, etc. They look good.
>
> Thank you in advance for your ideas!
>
> Regards,
> Jeff
next prev parent reply other threads:[~2003-05-14 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 22:26 Power On Self Test and testing memory Jeff Baitis
2003-05-14 22:34 ` Pete Popov [this message]
2003-05-15 0:27 ` Jeff Baitis
2003-05-15 2:43 ` Lyle Bainbridge
2003-05-15 2:43 ` Lyle Bainbridge
2003-05-15 14:38 ` Lyle Bainbridge
2003-05-15 18:03 ` Jeff Baitis
2003-05-14 22:56 ` Lyle Bainbridge
2003-05-14 22:56 ` Lyle Bainbridge
2003-05-14 23:00 ` Pete Popov
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=1052951641.788.225.camel@zeus.mvista.com \
--to=ppopov@mvista.com \
--cc=baitisj@evolution.com \
--cc=linux-mips@linux-mips.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