linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: Peter LaDow <petela@gocougs.wsu.edu>
Cc: Anatolij Gustschin <agust@denx.de>, linuxppc-dev@lists.ozlabs.org
Subject: Re: Failure to detect PCI card
Date: Mon, 05 Aug 2013 14:08:15 -0700	[thread overview]
Message-ID: <5200143F.9010307@ovro.caltech.edu> (raw)
In-Reply-To: <CAN8Q1EcnT3We1X22pw4AQ28xmd2d-XB9nTzZ2KdVb=qOx4j7-Q@mail.gmail.com>

Hi Pete,

>> 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.
>
> These are universal boards.  Our board does only support only 3V3 (and
> is slotted as such).

Ok.

>> 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.
>
> Hmm...I do have one.  But I can't get both the analyzer and the card
> in the system in at the same time.

My analyzer has an extender card that you first plug in, and then
plug the board into that ... any chance someone in your organization
has one of those cards? Alternatively, confirm the board works in
a machine that has more than one slot, and if it does not, use the
analyzer to see what is happening.

>> 3. Is debugging this PCI card worth your time?
>>
>>     Sometimes the "solution" involves tossing old hardware in
>>     the trash.
>
> Well, this is part of the ongoing work regarding the incoming PCI
> memory corruption.

Ok, I recall seeing that thread.

> We are going down the path of abandoning the 82540
> for our platform because we can't seem to track down the corruption.
> So we are looking at other chipsets which we can purchase, which
> include this National (now TI) chipset on the Netgear FA331.  If we
> could find a PCI (_not_ PCIe) card to test with that seems to work...
>
> Interestingly, I have an older 3com 3C905TXM exhibiting the same
> behavior.  Both of these are older cards (they even came with drivers
> on--gasp--floppies!).  Maybe the lack of a 5V supply is an issue...

If you're looking for a PCI target that you can completely control,
then if you have an "FPGA guy" in your company, perhaps he can
dig up a low-cost PCI card that you can configure as a PCI master
to emulate the functions of a network card.

Actually, before going down that route, I would get a PCI extender
that you can use to trace the traffic with your board. Does the
network card use 33MHz or 66MHz?

Cheers,
Dave

  reply	other threads:[~2013-08-05 21:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 17:58 Failure to detect PCI card Peter LaDow
2013-08-05 18:25 ` Anatolij Gustschin
2013-08-05 20:12   ` Peter LaDow
2013-08-05 20:27     ` David Hawkins
2013-08-05 20:49       ` Peter LaDow
2013-08-05 21:08         ` David Hawkins [this message]
2013-08-05 21:10           ` David Hawkins
2013-08-05 22:11           ` Peter LaDow
2013-08-05 23:07       ` Peter LaDow
2013-08-05 23:14         ` Peter LaDow
2013-08-06  2:01           ` David Hawkins
2013-08-08 20:31             ` Peter LaDow
2013-08-08 22:10               ` David Hawkins
2013-08-12  2:32               ` Benjamin Herrenschmidt
2013-08-12 16:52                 ` Peter LaDow
2013-08-06 20:03           ` Anatolij Gustschin
2013-08-05 18:32 ` Wolfgang Denk
2013-08-05 18:36   ` Peter LaDow

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=5200143F.9010307@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --cc=agust@denx.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=petela@gocougs.wsu.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).