From: Randy Vinson <rvinson@mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MPC832x EMDS and PCI expansion board
Date: Fri, 29 Jun 2007 11:11:59 -0700 [thread overview]
Message-ID: <46854B6F.10508@mvista.com> (raw)
In-Reply-To: <200706291038.15392.rparsons@cambridgebroadband.com>
Richard Parsons wrote:
> Hi Randy,
>
> Thanks for the hints :-) the hardware I have is the the Revision 1.0
> Prototype1 production (so the label on the board says so)
Maybe I mis-remembered then. All I know is that I experienced the same
phantom device problem you are seeing. Have you tried adding another PCI
card so both PMC2 and PMC3 are populated?
>
> Changing the Clock to 33Mhz didnt seem to do anything for me and still have
> lots of dumb PCI devices listed. Next I think I have to drag out the DSO and
> see what the bus wobbles look like (the reset is concerning to me, so it cant
> hurt to check it)
My PCI bus analyzer showed TRDY stuck low (plus another signal stuck low
but I can't remember the signal name since this was a while back.) All I
know is that with the 8349 and 8360 processor cards, I could configure
PCI in U-Boot and I could get to a U-Boot prompt even if the processor
card was not attached to the PIBs. I could also boot a Linux kernel w/
PCI support with or without the PIBs. With the 832x card, if I
configured PCI in U-Boot, the card would hang if it was not connected to
the PIBs.
>
> Could the Lowboot affect the PCI bus? ( but then I have tried low and highboot
> to no avail, so I dont think its that)
I don't think that makes a difference.
Randy V.
prev parent reply other threads:[~2007-06-29 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 14:22 [U-Boot-Users] MPC832x EMDS and PCI expansion board Richard Parsons
2007-06-28 20:20 ` Randy Vinson
2007-06-29 9:38 ` Richard Parsons
2007-06-29 18:11 ` Randy Vinson [this message]
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=46854B6F.10508@mvista.com \
--to=rvinson@mvista.com \
--cc=u-boot@lists.denx.de \
/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