public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] PCI-E problems on Kilauea board
Date: Wed, 11 Mar 2009 15:40:03 +0200	[thread overview]
Message-ID: <49B7BF33.5000403@embedded-sol.com> (raw)
In-Reply-To: <200903111322.50949.sr@denx.de>

Stefan Roese wrote:
> OK.
>
> I just tried this setup on my Kilauea board. Without any problems:
>
> U-Boot 2009.03-rc1-00050-g3aaf315 (Mar 11 2009 - 13:18:35)
>
> CPU:   AMCC PowerPC 405EX Rev. C at 400 MHz (PLB=200, OPB=100, EBC=100 MHz)
>        Security support
>        Bootstrap Option C - Boot ROM Location EBC (16 bits)
>        16 kB I-Cache 16 kB D-Cache
> Board: Kilauea - AMCC PPC405EX Evaluation Board
> I2C:   ready
> 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: successfully set as root-complex
>         01  00  8086  10b9  0200  00
> DTT1:  30 C
> Net:   ppc_4xx_eth0, ppc_4xx_eth1
>
> Type run flash_nfs to mount root filesystem over NFS
>
> Hit any key to stop autoboot:  4
>
> U-Boot 2009.03-rc1-00050-g3aaf315 (Mar 11 2009 - 13:18:35)
>
> CPU:   AMCC PowerPC 405EX Rev. C at 400 MHz (PLB=200, OPB=100, EBC=100 MHz)
>        Security support
>        Bootstrap Option C - Boot ROM Location EBC (16 bits)
>        16 kB I-Cache 16 kB D-Cache
> Board: Kilauea - AMCC PPC405EX Evaluation Board
> I2C:   ready
> DRAM:  256 MB
> FLASH: 64 MB
> NAND:  64 MiB
> PCI:   Bus Dev VenId DevId Class Int
> PCIE0: successfully set as root-complex
>         01  00  8086  10b9  0200  00
> PCIE1: link is not up.
> PCIE1: initialization as root-complex failed
> DTT1:  30 C
> Net:   ppc_4xx_eth0, ppc_4xx_eth1
>
> Type run flash_nfs to mount root filesystem over NFS
>
> Hit any key to stop autoboot:  0
> =>  
>
>
> The PCIe device used here is the Intel PRO/1000 PT Desktop card.
>
> Which Kilauea board revision are you using? And do you see the same problems 
> with other PCIe cards as well?
>
>   

I use Kilauea revision 1.2 and exactly the same network card as you.
The problem is still here. It doesn't happen with other PCI-E card I have
(10G Ethernet adapter).

I have a feeling that 2 Kilauea boards of the same revision may sometimes
exhibit different behavior with the same version of u-boot. For example,
with u-boot 2008.10-rc2 that comes with AMCC CD, memory was properly
detected on one board in bootstrap option B but not detected on the another.
I had to recompile u-boot and disable autocalibration to make things work
on this board.

Felix.

  reply	other threads:[~2009-03-11 13:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 16:44 [U-Boot] PCI-E problems on Kilauea board Felix Radensky
2009-02-17 14:16 ` Stefan Roese
2009-02-17 14:35   ` Felix Radensky
2009-02-17 14:44     ` Stefan Roese
2009-03-01 15:00       ` Felix Radensky
2009-03-02  8:37         ` Felix Radensky
2009-03-02  9:03           ` Stefan Roese
2009-03-02  9:32             ` Felix Radensky
2009-03-11 12:22               ` Stefan Roese
2009-03-11 13:40                 ` Felix Radensky [this message]
2009-03-11 14:05                   ` Stefan Roese
2009-03-11 14:42                     ` Felix Radensky
2009-02-17 17:18   ` Felix Radensky

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=49B7BF33.5000403@embedded-sol.com \
    --to=felix@embedded-sol.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