This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux: 66ak uboot

Tool/software: Linux

  • network topology, as shown in the diagram, we board has four pieces of 66ak14h, 66AK-A SGMII3 through the PHY to connect the TFPT server (192.168.2.10). 66AK-A kernel and file system has been loaded by TFTP, eth0~eth3 IP are set to 192.168.2.220~192.168.2.223.
  • 66AK-B uboot to run up,

             "Setenv ethact K2HK_EMAC"

             "Setenv IPADDR 192.168.2.11"

             "Ping 192.168.2.10"

              This is a ping pass, the kernel file system can be loaded by TFTP.

  • 66AK-C uboot run up after,

              "Setenv ethact K2HK_EMAC1"

              "Setenv IPADDR 192.168.2.12"

               "Ping 192.168.2.10"

               This time Ping impassability, 66AK-D also.

  • will be configured to DSP master, uses the GE_test(K2_STK_DSP_v1.1) to test, 66AK-A and 66AK-C can be completed through the SGMII1 transceiver interaction.
  • why the network is impassability in 66AK-C uboot running up?

     

  • Hi,

    When you execute ifconfig on 66AK-A, does it show you that all ethernet ports are up (especially SGMII1 & SGMII2)? Maybe you need to use ifup prior to trying to ping from 66AK-C & 66AK-D.

    Best Regards,
    Yordan
  • Hi,

         I execute ifconfig on 66AK-A, all ethernet ports are up (Included SGMII1 & SGMII2).

         I add debugging information to  test when 66AK-C  booting  , found that the data has been taken to the QMSS, but ultimately didn't sent to sgmii1, what are the reason that can cause this problem?

    Best Regards,