PCI scanning and devices initialization
Stefano.Gaiotto at marconi.com
Fri Aug 20 21:30:49 EST 2004
I examinated board schematics and I found that pin "IDSEL" of the bridge
PCI/PCMCIA (PCI1410) in wired (at least in the schematics...) to line AD12
of data/address bus. (What's device address? 12? or 2? or 16?)
With the help of the hardware boys I want now to chek signal integrity
Sylvain Munaut <tnt at 246tnt.com> on 18/08/2004 14:54:43
To: Stefano Gaiotto <Stefano.Gaiotto at marconi.com>,
"linuxppc-embedded at lists.linuxppc.org"
<linuxppc-embedded at lists.linuxppc.org>
Subject: Re: PCI scanning and devices initialization
Stefano Gaiotto wrote:
>I'm trying to use a device connected to a PCI bus, more exactly a
>with u-boot-1.1.1 and Linux (2.4.24 and 2.6.8) in a board with MPC8270.
>Both u-boot and Linux, during scanning procedure show me only the PCI
>bridge [1057/18c0] but I can't see the devices connected to the bus.
>I'm a novice with PCI bus and I'm not sure the board is good (is the first
>prototype) and so I'd like to know if scanning procedure should tell me
>connected or I have to do some device initialization before I can see them
>I suppose I should see them during scanning and then initialise them via
>If my assumption is true, shall I suppose my hardware is not good? Or
Yes, there may be something wrong with your hardware. I'm not familiar
with the MPC8270 PCI code but your devices should show up during scan.
At the PCI init, PCI devices don't yet have an address, so the host
detects them using configuration cycles. Theses uses a different
addressing scheme, using each address line as a kind of "chip select".
So the devices know the host is "talking" to it just by looking at it's
IDSEL line going asserted. If on your board the IDSEL isn't wired
properly then it won't work. Hopefully if that's the case, you can just
wire it by hand, it's not a high speed signal.
Also, I've come accross some simple FPGA implementation of PCI devices
that just didn't respond to config ...
PS: I'm not a PCI expert and that's just my understanding. There is
probably a lot of things that can go wrong.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-embedded