• State Resolved
  • Replies 7 replies
  • Subscribers 98 subscribers
  • Views 139 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

AM6442: mcu+ sdk: lwip, activating hostname leads to Enet IF down and MAC Port Link down

AM625: Enabling LWIP_NETIF_HOSTNAME cause "Network Link DOWN Event"

Endre
Prodigy 100 points
Part Number: AM625

Tool/software:

I basically observe the same as reported here (no solution given):

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1409369/am6442-mcu-sdk-lwip-activating-hostname-leads-to-enet-if-down-and-mac-port-link-down/5411378?tisearch=e2e-sitesearch&keymatch=Network%252520link%252520down%252520hostname#5411378

Everything works fine until I define LWIP_NETIF_HOSTNAME (I did it in the Makefile as I haven't gotten around to figuring which opt file to copy to my local project yet). Then I get a "Network Link DOWN Event" and I'm stuck in Waiting for Network UP.

I am using mcu_plus_sdk_am62x_11_00_00_16 and my (makefile) project is based on the lwip/enet_cpsw_udpclient/ example if I remember correctly.

Is somebody able to help me with this?

Endre

  • 0
    TI__Expert 3480 points

    Hi Endre,

    I was able to reproduce the problem. I will check with the stack behaviour, run some checks, and will get back to you in 3 days. 

    You can find the "LWIP_NETIF_HOSTNAME " being handled in the opt.h file in the following location: $(MCU_PLUS_SDK)/source/networking/lwip/lwip-stack/src/include/lwip/opt.h

    Thank you for your patience,
    Best regards,
    Teja.

  • 0 in reply to Teja Rowthu
    TI__Expert 3480 points

    Hi Endre,

    I have ran the tests again, and I have observed that the issue is not actually reproduceable from our end. The previous observation was because of a faulty network topology. I have set the LWIP_NETIF_HOSTNAME to be enabled, and ran the tests. The target is successfully acquiring IP address. Can you please check if you are able to reproduce the issue when the macro is set to 1 either in lwipopts.h or in the above mentioned opt.h path?

    Thanks and regards,
    Teja.

  • 0
    TI__Expert 3480 points

    Hi Endre,

    I am reopening this as requested. Can you please share the details requested in this E2E? I am not able to reproduce the behavior explained by you. I will try to reproduce the issue based on your inputs about your test setup.

    Thanks and regards,
    Teja.

  • 0 in reply to Teja Rowthu
    Prodigy 100 points

    Quote: What do you refer to when you say you are enabling LWIP_NETIF_HOSTNAME in runtime? Can you please elaborate? Please share the details regarding the logs you are observing during your tests in the former E2E.

    I do not enable it runtime. What I meant is that if I compile without LWIP_NETIF_HOSTNAME, everything works, as soon as I compile with LWIP_NETIF_HOSTNAME in opt.h, then I get the Enet IF DOWN Event messages.

    This is on a custom card, and we are using a different PHY, so could be related to that of course. If I have time (still a lot of pressure here), I can see I if I can reproduce it on an eval kit.

  • 0 in reply to Endre
    TI__Expert 3480 points

    Hi Endre,

    We were not able to reproduce the issue in our earlier setup. Please let us know if you could reproduce this on Eval kit. I will try to run this test again in our test bench, but due to other activities, this will take another week to finish.

    Please let us know if you need any further info.

    Thanks and regards,
    Teja.

  • +1 in reply to Endre
    TI__Expert 3480 points

    Hi Endre,

    Teja Rowthu said:
    You can find the "LWIP_NETIF_HOSTNAME " being handled in the opt.h file in the following location: $(MCU_PLUS_SDK)/source/networking/lwip/lwip-stack/src/include/lwip/opt.h

    Thanks for confirming the behavior. The expectation is that once the change has been done, we need to re-build the libraries as well as the example to get the change reflected. 

    Please reach out to us if you have any further queries.

    Regards,
    Teja.

  • 0 in reply to Teja Rowthu
    Prodigy 100 points

    I dug a bit more now, and the problem was fixed by setting the flag in opt.h as suggested, and recompiling the SDK libraries before building the application. I did not rebuild the SDK the last time I tried this.