[U-Boot-Users] PCI Enumeration

[John Manby]

Hi Rune,

Thanks for the quick reply.

I spoke with the custom DSP board designer about this and he assures me the
IDSEL settings are correct. He's done numerous PCI designs and thinking back
on it, I've never had more than one PCI device to deal with in a system
until now. He reminded me that one thing I left out in my initial
description is that both carrier cards have a transparent bridge on them.
That bridge would be in front of the non-transparent bridge on the
Valleytech board and in front of the DSPs on our custom board. I guess that
makes the depth two hops on our custom board and three on the Valleytech
board to get to the DSPs. I will read up on the PCI spec and look at the
bridge data sheets, but this level of PCI is new to me and I appreciate any
and all help. If you have any tips for debugging this in Linux, I would
appreciate that too! (I'm used to using Tornado or the Green Hills tools
with JTAG probes and this company doesn't have anything for debugging Linux)

Thanks again!!
-John

----- Original Message ----- 
From: "Rune Torgersen" <runet at innovsys.com>
To: "U-Boot-Users" <u-boot-users at lists.sourceforge.net>
Sent: Tuesday, January 13, 2004 9:59 AM
Subject: RE: [U-Boot-Users] PCI Enumeration


Start by getting the PCI spec.... PCI22.pdf is usually easy to find on
the net the 2.3 spec you will have to pay for.

Apart from that. Make sure that the IDSEL lines on the PCI connector is
driven by DIFFERENT address lines.
It sounds like your two slots use the same adress lines for IDSEL.


> I'm having an issue with U-Boot failing to recognize PCI devices on
bootup. I have a CompactPCI chassis
> with a PowerPC 405GP card and a Valleytech PCI carrier board with a TI
6415 DSP on it. The Valleytech
> board has an Intel non-transparent PCI bridge chip on it. I also have
a PCI carrier board with two custom
> mezzanine boards that have TI 6415 DSPs on them. We access the DSP PCI
interfaces directly on these
> boards. My problem is that the PCI bus fails to find one of the boards
when both are plugged in at the
> same time. If I only use the Valleytech board, I can talk to it fine;
conversely, if I only use our
> custom, board, it works. When both are plugged in, U-Boot only lists
the card device ID for the card
> furthest from the PPC. The PCI initialization also fails when I boot
the Debian kernel in this case. I
> need to be able to access both cards at the same time so I need to
resolve this.


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users