From: sudheer <urwithsudheer@gmail.com>
To: Raja Chidambaram <raja_chidambaram82@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: could not access the address in linux-System ace driver
Date: Thu, 31 Aug 2006 17:12:27 +0530 [thread overview]
Message-ID: <44F6CB23.3000802@gmail.com> (raw)
In-Reply-To: <20060831055304.53524.qmail@web53605.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 7730 bytes --]
Hello Raja,
Thanks for the reply.
Raja Chidambaram wrote:
> Hello Sudheer,
>
> Sorry for the Late reply.since we faced some
> complexity in this kind of system Ace setup we have
> dropped it & moved to different setup.
>
> As of now in your case trace the xilinx code which is
> bascially on adapter.c as for as the xilinix code is
> concerned the hardware initialization code are done
> by xilinux, And only the kernel integration code
> developed by open source developers.So u might to
> track
> this cahnges
>
> As u said your xilinx is connected to EBC make sure
> the power on cycles is perfomed with no errrors.
>
> As for as your base register for xilinux is concerned
> the u-boot handle same as linux but the AMCC 440SPe
> processor have differnet TLB type so please make
> sure u understand TLB for 440SPe.
>
>
>
Can you please send some links if available that tells about the TLBs in
440SPe. I have googled but could not get much information.
Thanks
Sudheer
>
>
>
>
>
> --- sudheer <urwithsudheer@gmail.com> wrote:
>
>
>> Hello All
>>
>> I'm really desperate for some help , I've been
>> struggling with this
>> system since few days.
>>
>> sudheer wrote:
>>
>>> Hello Raja,
>>>
>>> We too are working on customized board with amcc
>>>
>> 440SPe processor ,
>>
>>> xilinx System Ace controller. Compact flash is
>>>
>> connected to system
>>
>>> ace controller.
>>> We use u-boot 1.1.2 as bootloader & linux kernel -
>>>
>> 2.6.16-2.
>>
>>> System ace is connected to amcc440SPE processor
>>>
>> via GPIO and External
>>
>>> Peripheral Bus Controller(EBC).
>>>
>> I am still facing the issue in accessing the address
>> in linux.
>>
>> The physical address given in u-boot init.S
>> tlbentry for 'system ace'
>> is 0xE0000000
>> I am able to access the address in u-boot and
>> everything is fine in u-boot.
>> But in linux , I am able to ioremap the the address
>> 0xE0000000 but the
>> kernel crashes when i try to access the address .
>> physical address=0xe0000000
>> address_after_ioremap = 0xe1000000.
>> I am trying to read with
>> readw(address_after_ioremap)
>> The kernel gives an exception error saying Oops:
>> machine check, sig: 7
>> [#2] .
>> The error dump is as below:
>>
>> Instruction dump:
>> Data machine check in kernel mode.
>> PLB0: BEAR=0x00000000e0000000 ACR= 0xdb000000 BESR=
>> 0x0000000000008000
>> PLB1: BEAR=0xe98d7ad33716ee7e ACR= 0xdb000000 BESR=
>> 0x0000000000000000
>> POB0: BEAR=0x0000000fffaebbcd BESR0=0x00000000
>> BESR1=0x00000000
>> OPB0: BEAR=0x0000000000000000 BSTAT=0x00000000
>> Oops: machine check, sig: 7 [#2]
>> NIP: 00000000 LR: C0002200 CTR: 00000000
>> REGS: c0241f50 TRAP: 0202 Not tainted (2.6.16.2)
>> MSR: 00000000 <> CR: 84CA4124 XER: 00000000
>> TASK = dff6cb70[1] 'swapper' THREAD: c0740000
>> GPR00: 00000000 C0241E40 DFF6CB70 00000001 FFFFFFD0
>> 00000000 C0240000
>> C01F3C0C
>> GPR08: C01F0000 C0002200 00021002 C0001FF4 DFF6CD38
>> 802823E0 1FFB9600
>> 00000000
>> GPR16: 00000001 FFFFFFFF 00000000 007FFF00 1FFB3540
>> 1FF63CE0 1FFCEE78
>> C01C0000
>> GPR24: C01C0000 C01C0000 C01F0000 C01C0000 BFFFFFFF
>> FFFFFFD0 00000000
>> C0241F50
>> NIP [00000000] 0x0
>> LR [C0002200] ret_from_except+0x0/0x18
>> Call Trace:
>> Instruction dump:
>> Data machine check in kernel mode.
>> PLB0: BEAR=0x00000000e0000000 ACR= 0xdb000000 BESR=
>> 0x0000000000008000
>> .........and this dump gets print continously.
>>
>>
>> I have checked with TLB entries in u-boot and linux
>> using BDI:
>>
>> BDI_AMCC440SPe>tlb 0 10
>> IDX TID EPN SIZE VTS RPN USER WIMGE
>> USRSVC
>> 0 : 00 ff000000 16MB V0 -> 4_ff000000 U:0000 WI-G-
>> XWRXWR
>> 1 : 00 00000000 256MB V0 -> 0_00000000 U:0000 -I-G-
>> XWRXWR
>> 2 : 00 10000000 256MB V0 -> 0_10000000 U:0000 -I-G-
>> XWRXWR
>> 3 : 00 20000000 256MB V0 -> 0_20000000 U:0000 -I-G-
>> XWRXWR
>> 4 : 00 30000000 256MB V0 -> 0_30000000 U:0000 -I-G-
>> XWRXWR
>> 5 : 00 90000000 256KB V0 -> 4_00000000 U:0000 -I---
>> XWRXWR
>> 6 : 00 e0000000 1KB V0 -> 4_e0000000 U:0000 -I-G-
>> -WR-WR
>> 7 : 00 a0000000 4KB V0 -> 4_f0000000 U:0000 -I-G-
>> -WR-WR
>> 8 : 00 d0000000 256MB V0 -> c_00000000 U:0000 -I-G-
>> -WR-WR
>> 9 : 00 80000000 256MB V0 -> c_10000000 U:0000 -I-G-
>> -WR-WR
>> 10 : 00 01080000 1KB -0 -> 0_00000000 U:0000 -----
>> ------
>> BDI_AMCC440SPe>
>>
>> In Linux the tlb entries are as below.......
>>
>> BDI_AMCC440SPe>tlb 0 63
>> IDX TID EPN SIZE VTS RPN USER WIMGE
>> USRSVC
>> 0 : 0e 0ff1a000 4KB V0 -> 0_007ce000 U:0000 --MG-
>> --R--R
>> 1 : 0e 0fe94000 4KB V0 -> 0_1ff96000 U:0000 ---G-
>> X-RX-R
>> 2 : 0e 30017000 4KB V0 -> 0_007cd000 U:0000 --MG-
>> --R-WR
>> 3 : 0e 10039000 4KB V0 -> 0_1ffb8000 U:0000 ---G-
>> X-RX-R
>> 4 : 0e 30009000 4KB V0 -> 0_00758000 U:0000 ---G-
>> X-RX-R
>> 5 : 0e 30010000 4KB V0 -> 0_0078b000 U:0000 ---G-
>> X-RX-R
>> 6 : 0e 00000000 1KB -0 -> 0_1f4e2000 U:0000 ---G-
>> --R--R
>> 7 : 0e 0fe3e000 4KB V0 -> 0_1f4e2000 U:0000 ---G-
>> X-RX-R
>> 8 : 0e 0ff1c000 4KB V0 -> 0_007ed000 U:0000 --MG-
>> XWRXWR
>> 9 : 0e 0ff1e000 4KB V0 -> 0_007ee000 U:0000 --MG-
>> -WR-WR
>> 10 : 0e 0ff1f000 4KB V0 -> 0_007ea000 U:0000 --MG-
>> XWRXWR
>> 11 : 0e 0fe39000 4KB V0 -> 0_1ff8e000 U:0000 ---G-
>> X-RX-R
>> 12 : 0e 0ff21000 4KB V0 -> 0_007a8000 U:0000 --MG-
>> --R-WR
>> 13 : 0e 0fe47000 4KB V0 -> 0_1ffa9000 U:0000 ---G-
>> X-RX-R
>> 14 : 0e 0fe46000 4KB V0 -> 0_1ffb2000 U:0000 ---G-
>> X-RX-R
>> 15 : 0e 30019000 4KB V0 -> 0_007c5000 U:0000 --MG-
>> -WR-WR
>> 16 : 0e 0fe45000 4KB V0 -> 0_1ffa8000 U:0000 ---G-
>> X-RX-R
>> 17 : 00 fdfff000 4KB V0 -> 4_f0000000 U:0000 -IMG-
>> ----WR
>> 18 : 0e 0fe9a000 4KB V0 -> 0_1ff98000 U:0000 ---G-
>> X-RX-R
>> 19 : 0e 10067000 4KB V0 -> 0_0078e000 U:0000 --MG-
>> -WR-WR
>> 20 : 0e 00000000 4KB -0 -> 0_1f4e5000 U:0000 ---G-
>> --R--R
>> 21 : 0e 10030000 4KB V0 -> 0_1f4e5000 U:0000 ---G-
>> X-RX-R
>> 22 : 0e 10063000 4KB V0 -> 0_007b7000 U:0000 --MG-
>> -WR-WR
>> 23 : 0e 0fe4c000 4KB V0 -> 0_1ff9b000 U:0000 ---G-
>> X-RX-R
>> 24 : 0e 1007f000 4KB V0 -> 0_007e0000 U:0000 --MG-
>> -WR-WR
>> 25 : 0e 0ff1d000 4KB V0 -> 0_007c6000 U:0000 --MG-
>> --R-WR
>> 26 : 0e 0fe4e000 4KB V0 -> 0_1ffa1000 U:0000 ---G-
>> X-RX-R
>> 27 : 0e 0fe0f000 4KB V0 -> 0_0077e000 U:0000 ---G-
>> X-RX-R
>> 28 : 0e 0fe52000 4KB V0 -> 0_0077f000 U:0000 ---G-
>> X-RX-R
>> 29 : 0e 0fe53000 4KB V0 -> 0_1ff80000 U:0000 ---G-
>> X-RX-R
>> 30 : 0e 0fef9000 4KB V0 -> 0_1ff81000 U:0000 ---G-
>> --R--R
>> 31 : 0e 0fe3b000 4KB V0 -> 0_1ffa7000 U:0000 ---G-
>> X-RX-R
>> 32 : 0e 7f901000 4KB V0 -> 0_007db000 U:0000 --MG-
>> -WR-WR
>> 33 : 0e 10027000 4KB V0 -> 0_1ffd0000 U:0000 ---G-
>> X-RX-R
>> 34 : 0e 1003a000 4KB V0 -> 0_1ffb6000 U:0000 ---G-
>> X-RX-R
>> 35 : 0e 0fe51000 4KB V0 -> 0_00775000 U:0000 ---G-
>> X-RX-R
>> 36 : 0e 1003b000 4KB V0 -> 0_1ffb7000 U:0000 ---G-
>> X-RX-R
>> 37 : 0e 1002a000 4KB V0 -> 0_1ffcf000 U:0000 ---G-
>> X-RX-R
>> 38 : 0e 10066000 4KB V0 -> 0_007de000 U:0000 --MG-
>> -WR-WR
>> 39 : 0e 1002b000 4KB V0 -> 0_1ffd3000 U:0000 ---G-
>> X-RX-R
>> 40 : 0e 1002c000 4KB V0 -> 0_1ffd2000 U:0000 ---G-
>> X-RX-R
>> 41 : 0e 1005d000 4KB V0 -> 0_007f4000 U:0000 --MG-
>> XWRXWR
>> 42 : 0e 1002d000 4KB V0 -> 0_1ffc2000 U:0000 ---G-
>> X-RX-R
>> 43 : 0e 10028000 4KB V0 -> 0_1ffc8000 U:0000 ---G-
>> X-RX-R
>> 44 : 0e 10069000 4KB V0 -> 0_0078d000 U:0000 --MG-
>> -WR-WR
>>
>>
> === message truncated ===
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
[-- Attachment #2: Type: text/html, Size: 8443 bytes --]
next parent reply other threads:[~2006-08-31 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060831055304.53524.qmail@web53605.mail.yahoo.com>
2006-08-31 11:42 ` sudheer [this message]
2006-09-07 8:40 ` could not access the address in linux-System ace driver sudheer
2006-07-24 12:14 RE:SystemAce Driver Raja Chidambaram
2006-07-24 12:34 ` SystemAce Driver Ameet Patil
2006-08-09 15:06 ` sudheer
2006-08-11 9:34 ` Ameet Patil
2006-08-11 10:42 ` sudheer
2006-08-22 15:07 ` sudheer
2006-08-30 14:12 ` could not access the address in linux-System ace driver sudheer
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=44F6CB23.3000802@gmail.com \
--to=urwithsudheer@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=raja_chidambaram82@yahoo.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 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.