none
169.254 IP in Static Configuration RRS feed

  • Question

  • Hi All,

    I am facing an issue in WEC2013  static ip configuration.

    We have one setup where two SOM communicate with each other via Marvell network adapter on PCI.

    one SOM has WEC2013 OS and other one has linux on it. both have static IP configuration.

    But 1 in 100 times we get 169.254 IP after hard reboot at WEC2013 end.(we have no way to check/debug SOM having linux OS ).

    I tried Adapter rebind too, after rebind WINCE assigns 0.0.0.0 and then after a while 169.254 ip appears again.

    If we again reboot our device, we get valid ip.

    Also as both are communicating via PCI, we cant use wireshark to debug.

    Kindly guide us how to proceed/ debug this issue.

    Also what could be possible reasons for 169.254 ip in static ip configuration.

    Registry value:

    [HKEY_LOCAL_MACHINE\Comm\PCI\MARVELL_88E8059\Parms\TcpIp]
    "EnableDHCP"=dword:0
    "DefaultGateway"=multi_sz:"192.168.1.1"
    "IpAddress"=multi_sz:"192.168.1.1"
    "Subnetmask"=multi_sz:"255.255.255.0"

    "UseZeroBroadcast"=dword:0

    Best regards,

    Lokesh kumar

    Thursday, September 19, 2019 6:18 AM

All replies

  • Most likely this is an Ethernet driver issue, where it fails to properly initialize either the PHY (most likely) or the Ethernet hardware itself.

    Dump the Ethernet hardware and PHY registers in a working situation and in a non-working situation. It will most likely give you some hints as to what went wrong.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, September 19, 2019 9:12 AM
    Moderator
  • Lokesh

    What does "(we have no way to check/debug SOM having linux OS )." mean?  Do you have the same problem with Linux?


    Bruce Eitman
    Senior Enginer
    Bruce.Eitman AT Synopsys DOT com
    My BLOG http://geekswithblogs.net/bruceeitman
    I work for
    Synopsys

    Friday, September 20, 2019 1:51 PM
    Moderator
  • Hi Michel,

    Thanks for replying. we are trying to dump Ethernet and PHY registers as suggested.

    it will take some time to update our  observations from register dump as issue occurrence is rare.

    Best Regards,

    Lokesh Kumar

    Monday, September 23, 2019 5:49 AM
  • Hi Bruce,

    We have Two SOM's and the SOM having Linux OS is third party. so we don't have control over it.

    Our SOM(WEC2013) communicate with Linux OS SOM via Marvell Adapter.

    although we cannot make modifications/debugging in their SOM, we can ask for some specific log/checkpoint if you can suggest.

    Thanks and Best Regards,

    Lokesh Kumar

    Monday, September 23, 2019 6:00 AM
  • Do you have the same problem with Linux?

    Bruce Eitman
    Senior Enginer
    Bruce.Eitman AT Synopsys DOT com
    My BLOG http://geekswithblogs.net/bruceeitman
    I work for
    Synopsys

    Wednesday, September 25, 2019 12:26 PM
    Moderator