public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: sardamaxima <fhpworks@hotmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problem with PCI Express connecting 2 MPC8544
Date: Tue, 19 Jul 2011 09:09:28 -0700 (PDT)	[thread overview]
Message-ID: <32092567.post@talk.nabble.com> (raw)


I am trying to activate a PCIe link between two MPC8544 processor's on a
custom board.
One processor is configured as Root Complex(cfg_host_agt[0:2] = '111') and
the other processor as endpoint (cfg_host_agt[0:2] = '101').

 Only PCIe1 is active in both processors (cfg_IO_ports[0:2] = '010')

 In u-boot I set the following flags in both processors:

#define CONFIG_PCI           
#undef CONFIG_PCI1           
#define CONFIG_PCIE1           
#undef CONFIG_PCIE2         
#undef CONFIG_PCIE3         
#define CONFIG_FSL_PCI_INIT    
#define CONFIG_FSL_PCIE_RESET  

In the first processor (configured as RC) I get the following output(u-boot
1.3.0-rc3):
"
 pci_init_board: devdisr=7000008, io_sel=2, host_agent=7
    PCIE1 connected to Slot2 as Root Complex (base address e000a000)
...PCIE LTSSM=0x16, Negotiated link width=1
               Scanning PCI bus 01
    PCIE1 on bus 00 - 01 
...
"
the link is well negotiated but if i do  "pci" in u-boot console it only
shows one device:
"
=> pci
Scanning PCI devices on bus 0
BusDevFun  VendorId   DeviceId   Device Class       Sub-Class
_____________________________________________________________
00.00.00   0x1957     0x0033     Processor               0x20
"






 In the second processor (configured as EP) I get the following output:
"
...
   pci_init_board: devdisr=7000008, io_sel=2, host_agent=5

   PCIE1 connected to Slot2 as End Point (base address e000a000)
                Scanning PCI bus 00
 PCI Scan: Found Bus 0, Device 1, Function 0
        00  01  1957  0033  0b20  00
...
"
 Here i am using an old version of u-boot (1.3.0-rc3). It seems more
straightforward to work. I've considered updating to the latest u-boot but
since we had serious problems with DDR configuration and this has changed
considerably since the version I am using I am a little reluctant into an
update.


Someone give me a clue?

thanks a lot.

Daniel

-- 
View this message in context: http://old.nabble.com/Problem-with-PCI-Express-connecting-2-MPC8544-tp32092567p32092567.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

             reply	other threads:[~2011-07-19 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19 16:09 sardamaxima [this message]
2011-07-25 22:49 ` [U-Boot] Problem with PCI Express connecting 2 MPC8544 Swarthout Edward L-SWARTHOU
2011-07-26 10:01   ` HUGO MARTINS

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=32092567.post@talk.nabble.com \
    --to=fhpworks@hotmail.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