From: H L <swdevyid@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ppc4xx: PCI init failure on kilauea?
Date: Mon, 3 Mar 2008 09:29:36 -0800 (PST) [thread overview]
Message-ID: <889712.89118.qm@web45107.mail.sp1.yahoo.com> (raw)
Greetings from Austin, TX. My first posting to this list. Searched through the archives first, but didn't see any mention, so.....
On recently obtained new kilauea boards, I noted on all of them PCI init failure at boot:
U-Boot 1.3.1-g5dd372a2 (Jan 14 2008 - 11:01:38)
CPU: AMCC PowerPC 405EX Rev. A at 400 MHz (PLB=200, OPB=100, EBC=100 MHz)
Security support
Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
16 kB I-Cache 16 kB D-Cache
Board: Kilauea - AMCC PPC405EX Evaluation Board
I2C: ready
DTT1: 22 C
DRAM: 256 MB
FLASH: 64 MB
NAND: 64 MiB
PCI: Bus Dev VenId DevId Class Int
PCIE0: link is not up.
PCIE0: initialization as root-complex failed
PCIE1: link is not up.
PCIE1: initialization as root-complex failed
I did a git on ppc4xx and built/flashed that, but still seeing the same failure. Appears to die in ppc4xx_init_pcie_port() on the:
/*
* Verify link is up
*/
val = SDR_READ(SDRN_PESDR_LOOP(port));
if (!(val & 0x00001000)) {
val is coming back with a value of zero. This occurs whether or not any adapters are plugged into the PCIe slots. Anyone else seeing this?
thx,
LH
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20080303/20e9859e/attachment.htm
next reply other threads:[~2008-03-03 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 17:29 H L [this message]
2008-03-03 18:07 ` [U-Boot-Users] ppc4xx: PCI init failure on kilauea? Stefan Roese
2008-03-03 19:29 ` H L
2008-03-04 12:23 ` Stefan Roese
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=889712.89118.qm@web45107.mail.sp1.yahoo.com \
--to=swdevyid@yahoo.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