From: David Hawkins <dwh@ovro.caltech.edu>
To: "R. Ebersole (VTI - new)" <rje@valleytech.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mmap + segfaults on MPC8349E
Date: Sat, 08 Dec 2007 20:01:50 -0800 [thread overview]
Message-ID: <475B68AE.5000302@ovro.caltech.edu> (raw)
In-Reply-To: <475B5680.30303@valleytech.com>
Hi,
You haven't really provided enough information.
> We wrote some simple drivers/modules to mmap() FPGA registers to user space.
> At the moment, for testing, we reserve the upper x-MB of RAM, and mmap()
> there, instead.
1. The FPGA is located where? The local bus, or the PCI bus?
What frequency are you trying to operate at?
2. If its on the local bus, do you access it using GPCM or UPM?
Have you setup either correctly?
Have you confirmed the bus timing with a logic analyzer?
3. Have you created a bus functional model of the processor bus
that you have then run with your FPGA bus in ModelSim to
confirm that your FPGA performs correctly.
4. Have you tried burst and non-burst access by either using
DMA, or treating the memory area as cacheable or non-cacheable?
Have you checked those cases with simulation and then
with a scope or logic analyzer?
5. Did you try running stand-alone tests in U-Boot, to go for a
more bare-metal debug approach?
No point in debugging software if you have no idea whether the
hardware behaves. So confirm that you have tested your hardware
first.
My board design uses the MPC8349EA, I have an Altera Stratix II
FPGA on the local bus. I use GPCM to access flash on the local
bus via the FPGA, and UPM to access FPGA registers. I don't
have boards yet, but I've got a pretty good handle on how the
interface should work.
Cheers,
Dave
next prev parent reply other threads:[~2007-12-09 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 2:44 mmap + segfaults on MPC8349E R. Ebersole (VTI - new)
2007-12-09 4:01 ` David Hawkins [this message]
2007-12-11 1:53 ` R. Ebersole (VTI - new)
2007-12-11 2:16 ` David Hawkins
2007-12-15 6:40 ` R. Ebersole (VTI - new)
2007-12-15 19:55 ` David Hawkins
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=475B68AE.5000302@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rje@valleytech.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).