From: powerpc440 <powerpc440@googlemail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Problem with OPB access on 440GX and Linux 2.6.15
Date: Mon, 09 Oct 2006 15:46:28 +0200 [thread overview]
Message-ID: <452A52B4.1010303@googlemail.com> (raw)
Hi everybody,
I'm having a PPC440GX based board, based on Ocotea.
On the board is a Xilinx CPLD chip, connected with OPB (On-Chip
Peripheral Bus).
Under U-Boot I can communicate – reading and writing, without any
problems, but when the Linux kernel ones is loaded, then I'm getting
error message: “Bus error”. This error message appears on reading or
writing.
How I can access the units, which are connected with OPB?
There are the source code from the driver, that I use :
static void io_addr = ioremap(0x48300000, 0x100000); /* allocate 1MB
adress space */
long value = readl(io_addr + 0x7000);
and the error message:
VA: 0xe2180000
Machine check in kernel mode.
Data Read PLB Error
PLB0: BEAR=0x0000000048307000 ACR= 0x9b000000 BESR= 0x0c000000
POB0: BEAR=0x00000000040c0020 BESR0=0x00000000 BESR1=0x00000000
OPB0: BEAR=0x0000000000000000 BSTAT=0x00000000
Oops: machine check, sig: 7 [#4]
NIP: E107D078 LR: E107D068 CTR: 00000000
REGS: c0335f50 TRAP: 0202 Not tainted (2.6.16.27-himadef-0)
MSR: 00029000 <EE,ME> CR: 22004024 XER: 20000000
TASK = dfa1cc10[412] 'cat' THREAD: dcc54000
GPR00: E107D068 DCC55E80 DFA1CC10 00000010 00000010 E107D7AB D490F704
00000010
GPR08: 00000000 E2180000 00000000 FFFFFFFF 22004048 1001C334 00000000
00000400
GPR16: 00000001 100B0000 10014344 00000000 00000002 00000000 00000000
DDAC8600
GPR24: 00000000 DCC55EB8 DD3E5000 00000C00 E1080000 00000010 10014204
00001000
NIP [E107D078] sensor_proc_read+0x58/0x94 [himaio]
LR [E107D068] sensor_proc_read+0x48/0x94 [himaio]
Call Trace:
[DCC55E80] [E107D068] sensor_proc_read+0x48/0x94 [himaio] (unreliable)
[DCC55EB0] [C008C6EC] proc_file_read+0x2a4/0x354
[DCC55EF0] [C00564F0] vfs_read+0xcc/0x1a0
[DCC55F10] [C0057228] sys_read+0x4c/0x90
[DCC55F40] [C00019C4] ret_from_syscall+0x0/0x3c
Instruction dump:
7cf93b78 4800048d 80dce160 3ca0e108 38a5d7a0 7f43d378 7f64db78 48000485
813ce160 7c7d1b78 38c97000 7cc0342c <0c060000> 4c00012c 3ca0e108 7c7a1a14
Thanks in advance!
next reply other threads:[~2006-10-09 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 13:46 powerpc440 [this message]
2006-10-09 14:49 ` Problem with OPB access on 440GX and Linux 2.6.15 Gerhard Jaeger
2006-10-09 15:21 ` Jeff Mock
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=452A52B4.1010303@googlemail.com \
--to=powerpc440@googlemail.com \
--cc=linuxppc-embedded@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.