From: "André Schwarz" <Andre.Schwarz@matrix-vision.de>
To: kim.phillips@freescale.com
Cc: linuxppc-dev@ozlabs.org
Subject: MPC8343 - "unable to handle paging request @ 0"
Date: Sat, 05 Apr 2008 10:19:49 +0200 [thread overview]
Message-ID: <47F73625.9040903@matrix-vision.de> (raw)
Kim,
sorry for the general questions - but I'm running out of ideas.
We never ever had that many problems getting a PowerPC running during=20
the past 10 years.
I've cross-checked the hardware and design with Freescale FAE.=20
Everything looks fine and is approved.
We're running latest u-boot v1.3.2 and kernel 2.6.25-rc8 from Denx.
A MPC5200B System is up and running fine with this scenario, so=20
hopefully there are no basic problems.
The MPC8343B (rev.3.1) is working pretty fine with u-boot including=20
mtest. Only problem is a the TSECs not working with our RGMII phy - but=20
this can wait.
I've set up a dts based on the MPC834x_mds and removed the 2nd PCI bus=20
and local bus stuff.
Kernel has been build with a new platform "MVBLM7" which is the name of=20
our board - nothing special so far.
u-boot fills out all parameters (clocks, mem, initrd @ chosen, ...)=20
correctly and the kernel is started exactly the same way as the MPC5200B=20
system using "bootm kernel_add initrd_addr dtb_addr".
Kernel starts and crashes with "unable to handle kernel paging request @=20
00000000".
After turning debug on in some files I can see that the initrd memory=20
gets reserved and the dtb is parsed correctly.
PCI memory/io spaces are set up fine.
At first I thought this is a problem with the device tree since the call=20
trace always points to "of_"-functions and "strcmp".
So I removed nearly everything from the kernel and dts including PCI,=20
net, USB and peripherals leaving only a minimum (cpu, mem, soc-node with=20
ipic and serial).
Unfortunately the error is still the same !
I wonder if there are some basic issues regarding MPC8343 or=20
specialities from the Freescale boards not being present on our board.
Major difference is the CPU (MPC8343B), 512MB RAM (using 2 BATs of=20
course) and nothing else on the local bus besides the Nor-Flash.
Of course the MPC8343 has only a single PCI-32 and only one USB.
Do you have any hints on this ?
Do you suggest to wait for the 2.6.25 release ?
Do you know of any MPC8343 based boards already up and running ?
regards,
Andr=E9 Schwarz
MATRIX VISION GmbH, Talstra=DFe 16, DE-71570 Oppenweiler - Registergeric=
ht: Amtsgericht Stuttgart, HRB 271090
Gesch=E4ftsf=FChrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner
next reply other threads:[~2008-04-05 8:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 8:19 André Schwarz [this message]
2008-04-07 16:10 ` MPC8343 - "unable to handle paging request @ 0" Scott Wood
2008-04-08 8:51 ` Andre Schwarz
2008-04-08 16:43 ` Scott Wood
2008-04-08 13:50 ` Andre Schwarz
2008-04-08 16:48 ` Scott Wood
2008-04-08 19:59 ` André Schwarz
2008-04-09 12:54 ` Andre Schwarz
2008-04-09 18:57 ` Scott Wood
2008-04-09 19:09 ` Andre Schwarz
2008-04-09 19:15 ` Scott Wood
2008-04-10 9:00 ` Andre Schwarz
2009-12-04 22:55 ` MPC8343EA Linux DTS file agnel
2009-12-04 22:56 ` agnel
2009-12-04 23:39 ` Kim Phillips
[not found] ` <72d214170912041543g207837a5v67c9bb157e0a2c8b@mail.gmail.com>
2009-12-05 1:47 ` Kim Phillips
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=47F73625.9040903@matrix-vision.de \
--to=andre.schwarz@matrix-vision.de \
--cc=kim.phillips@freescale.com \
--cc=linuxppc-dev@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).