From: Gerhard Jaeger <g.jaeger@sysgo.com>
To: "Iñigo Lopez Barranco" <ilopez@albatros-sl.es>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Lite5200 PCI not working
Date: Mon, 21 Jun 2004 13:48:35 +0200 [thread overview]
Message-ID: <200406211348.35398.g.jaeger@sysgo.com> (raw)
In-Reply-To: <42A622EB18325843894BB8E1040E3DF5022754@sinaexchf>
Hi,
On Monday 21 June 2004 13:12, Iñigo Lopez Barranco wrote:
> >I don't understand, what do you mean "with both power LEDs off",
> > the LEDs on the Lite5200? If yes, then I guess you have a problem!
>
> Yes, I mean that. If the PCI card is plugged in the slot, when I connect
> the power, the LEDs in the Lite5200 board for 5V and 3.3V stay off.
--> short-circuit, I'm really surprised, that the board survived, sometimes,
ground connections from the PCI card tend to go up in smoke :-(
> Without the PCI card, the Lite5200 works fine.
>
> > And of course it should be inserted correctly - sorry if this is too
> > obvious!
>
> I think it is, but just to be sure: when I plug the card the RJ45 connector
> is in the side of the IDE connector of the Lite5200, in the opposite side
> of the "short part" of the PCI connector. Right?
NO NO!!! See Wolfgangs mail:
>>"You may have plugged it in incorrectly. Make sure that the front
>>bezel is on the side where the serial and USB connectors are - i. e.
>>NOT where the ATA connector is."
accoding to this, the part with the RJ45 connector should be on
the USB & serial connector side and NOT the way you did it now.
If in doubt, check the schematics and compare with the PCI specification...
>
> > One card, that is known to work in this slot is the Intel eepro100 NIC.
>
> I'll try to get ont of those, though I'm not sure if the timing problems in
> the PCI bus may cause the problem I'm seeing with this board. Thanks.
Probably not, but it is a hint, in case you encounter more PCI problems, when
the LEDs are on again ;-)
Ciao,
Gerhard
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-21 11:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 11:12 Lite5200 PCI not working Iñigo Lopez Barranco
2004-06-21 11:48 ` Gerhard Jaeger [this message]
[not found] <20040708124140.E18E4C109F@atlas.denx.de>
2004-07-08 13:34 ` Stefan Nickl
-- strict thread matches above, loose matches on Subject: below --
2004-07-01 9:18 Wolfgang Denk
2004-07-01 11:36 ` Kate Alhola
2004-07-01 12:38 ` Stefan Nickl
2004-07-01 22:20 ` Kate Alhola
2004-07-01 22:29 ` Wolfgang Denk
2004-07-02 4:43 ` Kate Alhola
2004-07-02 7:22 ` Wolfgang Denk
2004-07-02 7:55 ` Kate Alhola
2004-07-02 8:51 ` Wolfgang Denk
2004-07-08 11:57 ` Stefan Nickl
2004-07-08 12:12 ` Wolfgang Denk
2004-06-21 10:03 Iñigo Lopez Barranco
2004-06-21 10:26 ` Gerhard Jaeger
2004-06-21 10:53 ` Wolfgang Denk
2004-06-21 11:39 ` Gerhard Jaeger
2004-06-21 14:12 ` Kate Alhola
2004-06-21 15:14 ` Wolfgang Denk
2004-06-21 16:20 ` Kate Alhola
2004-07-01 8:41 ` Stefan Nickl
2004-07-01 8:52 ` Wolfgang Denk
2004-06-21 10:51 ` Wolfgang Denk
2004-06-21 19:19 ` Mark Jonas
2004-06-22 6:08 ` Gerhard Jaeger
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=200406211348.35398.g.jaeger@sysgo.com \
--to=g.jaeger@sysgo.com \
--cc=ilopez@albatros-sl.es \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).