Problems with PCIe after 3.10? (u-boot logs)

Hey @pepe,

I am hoping you (or someone else) can help with the problem I mentioned in another thread. I now have u-boot and dmesg via USB/TTL. My problem is that (after 3.10 upgrade):

  1. WLAN card in slot 3 is usually not detected (it is not the card)
  2. mSATA card in slot 1 is ususally not detected (it is not the SSD)

I should mention now that I have 2 TOs and 6 WLAN cards. All 6 work in my working TO, but of all 5 cards tested in this TO, all have had problems.

My impression is that after the machine is turned off for a while (i.e. allowed to cool), I have the best chance of detecting the card.

Interestingly, the mPCIe card in slot 3 is not detected during u-boot! I have u-boot logs of both outcomes, below. FWIW, I tried env default -a in u-boot.

This is a successful u-boot log:

U-Boot SPL 2015.10-rc2 (Aug 18 2016 - 20:43:35)
High speed PHY - Version: 2.0
SERDES0 card detect: SATA

Initialize Turris board topology
Detected Device ID 6820
board SerDes lanes topology details:
 | Lane #  | Speed |  Type       |
 --------------------------------
 |   0    |  6   |  SATA0       |
 |   1    |  5   |  USB3 HOST0  |
 |   2    |  5   |  PCIe1       |
 |   3    |  5   |  USB3 HOST1  |
 |   4    |  5   |  PCIe2       |
 |   5    |  0   |  SGMII2      |
 --------------------------------
poll_op_execute: TIMEOUT
:** Link is Gen1, check the EP capability
PCIe, Idx 1: remains Gen1
:** Link is Gen1, check the EP capability
PCIe, Idx 2: remains Gen1
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver TIP-1.29.0
Memory config in EEPROM: 0x02
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR3 Training Sequence - Ended Successfully


U-Boot 2015.10-rc2 (Aug 18 2016 - 20:43:35 +0200), Build: jenkins-omnia-master-23

SoC:   MV88F6820-A0
       Watchdog enabled
I2C:   ready
SPI:   ready
DRAM:  2 GiB (ECC not enabled)
Enabling Armada 385 watchdog.
Disabling MCU startup watchdog.
Regdomain set to **
MMC:   mv_sdh: 0
SF: Detected S25FL164K with page size 256 Bytes, erase size 64 KiB, total 8 MiB
PCI:
  00:01.0     - 168c:003c - Network controller
PCI:
  01:00.0     - 11ab:6820 - Memory controller
  01:01.0     - 168c:0033 - Network controller
Model: Marvell Armada 385 GP
Board: Turris Omnia SN: 0000000B00010AF7
Regdomain set to **
SCSI:  MVEBU SATA INIT
SATA link 0 timeout.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
Net:   neta2
Hit any key to stop autoboot:  0
Setting bus to 1
BOOT eMMC FS
BtrFS init: Max node or leaf size 4096
2715688 bytes read in 353 ms (7.3 MiB/s)
BtrFS init: Max node or leaf size 4096
17306 bytes read in 171 ms (98.6 KiB/s)
Kernel image @ 0x1000000 [ 0x000000 - 0x297028 ]
## Flattened Device Tree blob at 02000000
   Booting using the fdt blob at 0x2000000
   Loading Device Tree to 0fff8000, end 0ffff399 ... OK

Starting kernel ...

Variation 1 (below) results in failure to see the WLAN card in slot 3 (via a lspci):

poll_op_execute: TIMEOUT
:** Link is Gen1, check the EP capability
PCIe, Idx 1: remains Gen1
PCIe, Idx 2: detected no link
High speed PHY - Ended Successfully

Variation 2 (below) seems to have no effect(?):

MMC:   mv_sdh: 0
SF: Detected S25FL164K with page size 256 Bytes, erase size 64 KiB, total 8 MiB
*** Warning - bad CRC, using default environment

PCI:

Variation 3 (below) has no effect upon card detection (!!):

PCI:
  00:01.0     - 168c:003c - Network controller
Model: Marvell Armada 385 GP

Using a bitmask for variations 1, 2 and 3:
000 : detected
001 : detected (!!)
010 : (not yet seen)
101 : not detected
110 : not detected
111 : not detected

Any idea? Or a hardware issue?

Hello,
I’ve just replied to you via e-mail, which you sent to tech.support@turris.cz. :slight_smile:
Let’s focus our conversation there.