From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Robert Woodworth" <rwoodworth@securics.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MMU failure, Virtex4-FX60
Date: Mon, 7 Jan 2008 11:21:21 -0700 [thread overview]
Message-ID: <fa686aa40801071021g611ee7d6jbeafb4616cf29464@mail.gmail.com> (raw)
In-Reply-To: <1199727744.17452.8.camel@PisteOff>
On 1/7/08, Robert Woodworth <rwoodworth@securics.com> wrote:
> Hello!
>
> I'm building a new Virtex4-FX60 device. I have built it with the new
> MPMC3 and a 256MB SO-DIMM. It works successfully with a "mem-test" type
> embedded program.
>
> I cannot get it to boot a Linux kernel. I have traced it down to the
> MMU not getting mapped correctly.
>
> I can load the kernel via jtag, get the pre-boot messages on the serial
> but then when it tries to jump to 0xc0002218 (start_here: head_4xxx.S)
> it fails with a "Machine check exception; invalid instruction address".
>
> Using the debugger and examining the memory once the mmu is suppose to
> be configured, I see that it is not mapping 0xc0000000 to the proper
> location. I'm sure I've set something up wrong in my FPGA and I need to
> re-synthesize. But what?
Hmmm, I haven't seen that failure mode before. MMU handling on an of
my virtex platforms has never been a problem. Take a look at the TLB
registers to see how they are configured to see if the mappings are
really getting written.
What kernel version are you using?
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2008-01-07 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 17:42 MMU failure, Virtex4-FX60 Robert Woodworth
2008-01-07 18:21 ` Grant Likely [this message]
2008-01-08 21:54 ` Robert Woodworth
2008-01-09 16:46 ` Stephen Neuendorffer
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=fa686aa40801071021g611ee7d6jbeafb4616cf29464@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rwoodworth@securics.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;
as well as URLs for NNTP newsgroup(s).