Hi Pete,
On Mon, Aug 5, 2013 at 11:25 AM, Anatolij Gustschin <ag...@denx.de> wrote:
Maybe this card needs bigger delay to respond after PCI reset. You can
try to re-build U-Boot with defined CONFIG_PCI_BOOTDELAY. Use 1000
for CONFIG_PCI_BOOTDELAY in the first step and if detection works,
try to decrease this value.
That didn't work. But perhaps the problem is because these are older
PCI parts, and don't implement ECAM (only the older CAM)? I don't
think u-boot limits itself...
Since you're looking for suggestions (apologies if these are
"too obvious");
1. Have you checked the power supplies on the PCI board?
PCI boards can be powered from 3.3V or 5V, or both. I've had
old PCs that only supply one or the other rail, and various
evaluation boards that only supply 3.3V.
If you can put together a "working" x86 setup that detects the
board, then you could poke around and see what voltages exist
on some of the decoupling components, then plug it into your
real system, and see what voltages you measure there.
2. Have you probed the PCI bus using a bus analyzer or scope?
If you have a PCI bus analyzer (or can find someone with one),
plug it in and see what happens at power-on (there should be
configuration cycles).
At a minimum, if you have a 'scope, see if the PCI configuration
space access handshakes are active during power-on.
3. Is debugging this PCI card worth your time?
Sometimes the "solution" involves tossing old hardware in
the trash.
Cheers,
Dave
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
