Re: Problem in PCI initialization

["G.Muruganandam" <gmuruga@gdatech.com>]

[-- Attachment #1: Type: text/plain, Size: 4700 bytes --]


Before testing the PCI in linux, you need to make 
sure that the PCI is working under u-boot with out any issues.

Here are the check list.

1. pci long command under u-boot should display 
the pci configuration registers of the device in PCI bus
     consistently.

2. Check the PCI BAR registers at offset 
0x10,0x14 and 0x18 are configured with proper values based on
     whether it is a PCI memory mapped device or IO mapped device.

3. Check the TLB setting under U-boot whether it 
is set correctly for the PCI memory and/or IO regions.
    If you are using the u-boot 1.1.x, you should 
look at init.S for the particular board/cpu.

Hope this helps!

Thanks
G.Muruganandam


At 11:39 PM 6/14/2006, Prabhat_Singh wrote:
>Content-class: urn:content-classes:message
>Content-Transfer-Encoding: 7bit
>Content-Type: multipart/alternative;
>         boundary="----_=_NextPart_001_01C69046.65DE2215"
>
>Hi all
>I am using MPC8248 based board which has got one PCI interface at 66 MHz .
>
>I am not able to initialize PCI, I am really 
>clueless and getting the following errors.
>
>Can any one tell me what is wrong with this?
>
>But I am initializing the pci in uboot also and 
>there in uboot able to detect the network card, 
>but while boot its give first time the machine 
>check exception and then its reseting itself and 
>then in second try it (uboot) is working fine. 
>Do the register sets in uboot is again read by 
>linux during linux PCI initialization?
>
>Someone please help.
>
>## Booting image at ffd00000 ...
>Image Name: Linux-2.4.28-1.3.1-517
>Image Type: PowerPC Linux Kernel Image (gzip compressed)
>Data Size: 643461 Bytes = 628.4 kB
>Load Address: 00000000
>Entry Point: 00000000
>Verifying Checksum ... OK
>Uncompressing Kernel Image ... OK
>## Current stack ends at 0x01FAB390 => set upper limit to 0x00800000
>No initrd
>## Transferring control to Linux (at address 00000000) ...
>Memory BAT mapping: BAT2=32Mb, BAT3=0Mb, residual: 0Mb
>
>Linux version 2.4.28-1.3.1-517 
>(root@localhost.localdomain) (gcc version 3.3.4) 
>#280 Tue Jun 13 16:17:02 IST 2006
>
>On node 0 totalpages: 8192
>
>zone(0): 8192 pages.
>
>zone(1): 0 pages.
>
>zone(2): 0 pages.
>
>Kernel command line: console=ttyS0,115200 root=1f00
>
>Calibrating delay loop... 266.24 BogoMIPS
>
>Memory: 30712k available (1228k kernel code, 368k data, 64k init, 0k highmem)
>
>Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
>
>Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
>
>Mount cache hash table entries: 512 (order: 0, 4096 bytes)
>
>Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
>
>Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
>
>POSIX conformance testing by UNIFIX
>
>PCI: Probing PCI hardware
>
>Scanning bus 00
>
>Oops: kernel access of bad area, sig: 11
>
>NIP: C000C6DC XER: 00000000 LR: C0003FAC SP: 
>C0183DC0 REGS: c0183d10 TRAP: 0300 Not tainted
>
>MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
>
>DAR: 00000024, DSISR: 20000000
>
>TASK = c023a000[14] '¢pÀ }¬' Last syscall: -1
>
>last math 00000000 last altivec 00000000
>
>GPR00: 00000000 C0183DC0 C023A000 C0183E80 
>00000024 20000000 C0170000 00000439
>
>GPR08: 00000000 C0183D20 00000000 00000000 
>22004084 B5FFFFFF 01FF8000 007FFC1E
>
>GPR16: 00000001 00000000 FFFFFFFF 007FFC00 
>00001032 00183E70 00000000 C0003FAC
>
>GPR24: 00000000 00030001 00000008 20000000 
>C0183E80 00000024 00000024 00000008
>
>Call backtrace:
>
>C0019384 C0003FAC 00000000 C0003FAC 00000000 C0003FAC C0184214
>
>C0003FAC C0184380 C0003FAC C01844F0 C0003FAC C0184664 C0003FAC
>
>C01847D0 C0003FAC C0184940 C0003FAC C0184AB4 C0003FAC C0184C24
>
>C0003FAC C0184D94 C0003FAC C0184F04 C0003FAC C0185074 C0003FAC
>
>00000000 C0003FAC 00000000 C0003FAC 00000000
>
>Kernel panic: Aiee, killing interrupt handler!
>
>In interrupt handler - not syncing
>
><0>Rebooting in 180 seconds..
>
>
>
>DISCLAIMER:
>This email (including any attachments) is 
>intended for the sole use of the intended 
>recipient/s and may contain material that is 
>CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. 
>Any review or reliance by others or copying or 
>distribution or forwarding of any or all of the 
>contents in this message is STRICTLY PROHIBITED. 
>If you are not the intended recipient, please 
>contact the sender by email and delete all 
>copies; your cooperation in this regard is appreciated..
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded

[-- Attachment #2: Type: text/html, Size: 5666 bytes --]