On Fri, Jul 7, 2017 at 4:50 PM, Stephen Warren swarren@wwwdotorg.org wrote:
On 07/06/2017 09:57 PM, Simon Glass wrote:
Hi Stephen,
On 6 July 2017 at 12:55, Stephen Warren swarren@wwwdotorg.org wrote:
On 07/06/2017 11:36 AM, sjg@google.com wrote:
Update the tegra pci driver to support a live device tree. Fix the check for nvidia,num-lanes so that an error will actually be detected.
Simon,
Something in the latest u-boot-dm/master branch breaks PCI or Ethernet on Jeton TK1 and TX1. I don't know which patch it is. test/py's ping test simply fails due to lack of any Ethernet adapter. I don't see any errors during either boot or the network test setup scripts, which include "pci enum":
TK1 (built-in RTL8169 PCI Ethernet): Tegra124 (Jetson TK1) # ping $serverip No ethernet found. ping failed; host 192.168.100.1 is not alive Tegra124 (Jetson TK1) #
TX1 (add-on RTL8169 PCI Ethernet): Tegra210 (P2371-2180) # pci enum ERROR: tegra-pcie: failed to power on PHY: -110 at /var/lib/jenkins/workspace/u-boot-denx_uboot_dm-master-build/src/u-boot/drivers/pci/pci_tegra.c:774/tegra_pcie_enable_controller() ERROR: tegra-pcie: failed to enable controller at /var/lib/jenkins/workspace/u-boot-denx_uboot_dm-master-build/src/u-boot/drivers/pci/pci_tegra.c:1154/pci_tegra_probe() Tegra210 (P2371-2180) # setenv autoload no Tegra210 (P2371-2180) # dhcp No ethernet found. Tegra210 (P2371-2180) #
I also retested u-boot/master to make sure there's no test system infrastructure issue (that branch passes), and re-ran the failing test 3 times on TK1 with identical results. Other Tegra boards that I test all seem fine, at least as far as passing test/py.
P.S. I'll be away next week and the week after. Tom Warren may be able to monitor the test system emails, but I don't think I've set him up with access to e.g. retrigger tests etc.; perhaps I should look into that...
As mentioned elsewhere that error (failing to power on PHY) happens for me always on my TK1 (and has for about a year) because it seems to have a broken PMIC. I do have a TX1 somewhere but cannot find it despite much searching.
I'm very puzzled that you claim your TK1 always has this issue; this issue is clearly not present in mainline U-Boot (unless it's very intermittent and my test system has got lucky, but it's very reproducible so I don't think so), and I don't believe there's anything in the the PMIC that can be altered permanently; the boot configuration is in OTP (One Time Programmable) memory (fuses?) and can't be changed. Are you absolutely 100% sure that you cleanly replaced your development version of U-Boot correctly and tested with a 100% unmodified mainline U-Boot? Also, please try (a) flashing unmodified mainline U-Boot (b) disconnecting EVERY cable from the TK1 and leaving it that way for 10 minutes to drain any capacitors (or perhaps even overnight) (c) powering up to see if any problems still exist.
I've never seen this on my device, but one of the Fedora QA devices has similar issues with vanilla upstream u-boot, I wondered whether it was a slightly different HW rev.
Peter