U-Boot Driver for Ethernet Controller

Technical Support
, , , ,
81

Ok. thanks for the info. When will 2.7b4 Q3 be available?

82

At the beginning of Q4 aka early October.

83

Have there been changes between Apalis TK1 2GB V1.1A and V1.2A which could impact the reliability of the physical link establishment? (As we will use V1.2A at some point in time I would skip the tests of the physical link if there could be an impact.)

84

Some minor new errata(s) got integrated which may have some influence I guess. Unfortunately the PCN which will detail this is not quite ready yet. That said as mentioned before we are not aware of any existing such issues really.

85

Hi Marcel, I ran the test script (repeated cold-start + try to ping the SOM) with Apalis TK1 Linux BSP v2.7b3 non-mainline and our custom baseboard as carrier. It seems like the physical link establishment is quite stable. I would like to track down the possible root cause(s) for the physical link missing more often in our image and need some more information about the u-boot patch:

  • When is tegra_pcie_board_port_reset() and potentially other functionalities of the u-boot patch to fix “pci devices not listed” executed? Is it only executed when the u-boot command pci enum (e.g. as part of a TFTP update setup) or some other ethernet functionality is used? Or are patch functionalities executed in every case even if the ethernet is not used in u-boot at all?
  • When is tegra_pcie_board_port_reset() and potentially other functionalities of the u-boot patch to fix “missing physical link” executed? (same as above)