17 Replies Latest reply on Jun 26, 2018 9:25 AM by Carlos_A

    Broadwell-DE No MDC/MDIO

    Mikeliu Green Belt



      Problem: No MDC/MDIO signal

      CPU: Broadwell-DE SoC, 4Core/8T

      10G BASE –T PHY: Intel, X557-AT

      Flash Image:

      1. BDXDE_KR_BACKPLANE_LED_LO_NO_MNG_1.13v02_800006D1.bin

      2. BDXDE_10GBASET_NO_MNG_1.13v02_800006B7.bin



      ===========Eth Info==================

      root@genericx86-64:/dni# ethtool -i eth1

      driver: ixgbe

      version: 5.0.0-k

      firmware-version: 0x800006a8


      bus-info: 0000:04:00.0

      supports-statistics: yes

      supports-test: yes

      supports-eeprom-access: yes

      supports-register-dump: yes

      supports-priv-flags: yes

      ===========Eth Info End==================

      04:00.0 Ethernet controller: Intel Corporation Ethernet Connection X552 10 GbE Backplane

      04:00.1 Ethernet controller: Intel Corporation Ethernet Connection X552 10 GbE Backplane




      We try to do MDI single r/w through MSCA(0x0000425c) and MSRWD(0x00004260).

      The rule and steps is shown below



      04:00.0   [Base address]   + [offset]      [32 bits] [value]

      devmem 0x383fff400000+0x0000425c 32 0x501dc501           //Address cycle    PHYAD = 0x00

      devmem 0x383fff400000+0x00004260 32 0x00002001          //Test Mode 1

      devmem 0x383fff400000+0x0000425c 32 0x541dc501          //Write operation



      Is it correct?



      We also try to use the tool of "lanconf64e" doing "IEEE Tests", but we still cannot got MDC/MDIO signal.

      Then, we upgrade flash to BDXDE_10GBASET_NO_MNG_1.13v02_800006B7.bin.

      However, the situation is the same.



      Another question is when we use BDXDE_10GBASET_NO_MNG_1.13v02_800006B7.bin, the eth cannot link up.

      If we change the image to XXX_BACKPLANE..., it can link up in 1G. But, 10G doesn't work...



      Why we can't get MDC/MDIO signal?

      In backplane mode, why X557 only link up in 1G?


      Could you give us some suggestions?




        • Re: Broadwell-DE No MDC/MDIO
          Carlos_A Brown Belt

          Hello, Mikeliu:


          Thank you for contacting Intel Embedded Community.


          In order to better understand your consultation, we want to address the following questions:


          Could you please tell us if the affected project is a third party one or it has been developed by you? In case that it is a third party design, please give us all the information related to it. On the other hand, if it is your design, could you please inform us where is stated the information used to develop the affected project? How many units have been manufactured? How many are affected? And, what is the failure rate?


          Could you please inform us the part numbers and SKU’s of the processor and chipset related to this situation?



          Could you clarify us if the Ethernet device is an add-in card or it is part of the affected board? Please give us all the information related to this Ethernet device.



          Could you please let us know where do you download the files related to this condition?


          Please let us know all the information that should answer our questions.


          Waiting for your update.


          Best regards,


            • Re: Broadwell-DE No MDC/MDIO
              Mikeliu Green Belt

              Hi Carlos_A,


              This project is in develop. We manufactured several samples and all of these samples had the same situation.


              The phy's datasheet we reference is shown below.



              CPU Info:


              root@genericx86-64:/dni# cat /proc/cpuinfo

              processor       : 0

              vendor_id       : GenuineIntel

              cpu family      : 6

              model           : 86

              model name      : Intel(R) Xeon(R) CPU D-1527 @ 2.20GHz

              stepping        : 3

              microcode       : 0x700000e

              cpu MHz         : 801.904

              cache size      : 6144 KB

              physical id     : 0

              siblings        : 8

              core id         : 0

              cpu cores       : 4

              apicid          : 0

              initial apicid  : 0

              fpu             : yes

              fpu_exception   : yes

              cpuid level     : 20

              wp              : yes

              flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 intel_ppin intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts

              bugs            :

              bogomips        : 4400.03

              clflush size    : 64

              cache_alignment : 64

              address sizes   : 46 bits physical, 48 bits virtual

              power management:




              The document we reference is shown below.




            • Re: Broadwell-DE No MDC/MDIO
              Mikeliu Green Belt



              What the kernel config or driver should be installed if we want to use MDC/MDIO in broadwell D1500?

              We already enable MDIO, MDIO_DEVICE and IXGBE now.

              Is there anything else missing?


              Another question is how to check the NVM is configured to use MDIO functions, because the MDIO and LED functions share the same interface pins.

              Is it probably the reason why we can't get MDC/MDIO signal?