i.MX ProcessorsのトピックRe: NETIF driver doesn't rise up the NETIF_FLAG_LINK_UP flag

NETIF driver doesn't rise up the NETIF_FLAG_LINK_UP flag

MichalKv — Tue, 19 Mar 2024 08:59:36 GMT

Hello,

I'm getting a weird behaviour while trying to run UDP communication on MIMXRT1170-EVK board.

The communication is supposed to run on CM4 core whose code is moved into the SDRAM (starting address: 0x80000000). Now I'm debugging only CM4 core so the CM7 shouldn't have any effect on the behaviour or atleast that's what I would expect.

Now get to the strange behaviour. I'm using the 100M ethernet connector which is supposed to work as UDP communication (and modbus later). I initialize the communication basically through this sequence (it's basically the lwip_ping_cm4 example) :

IP4_ADDR(&netif_ipaddr, configIP_ADDR0, configIP_ADDR1, configIP_ADDR2, configIP_ADDR3); IP4_ADDR(&netif_netmask, configNET_MASK0, configNET_MASK1, configNET_MASK2, configNET_MASK3); IP4_ADDR(&netif_gw, configGW_ADDR0, configGW_ADDR1, configGW_ADDR2, configGW_ADDR3); lwip_init(); netif_add(netif, &netif_ipaddr, &netif_netmask, &netif_gw, &enet_config, NETIF_INIT_FN, ethernet_input); netif_set_default(netif); netif_set_up(netif);

It works fine, I'm able to PING the device, send message from PC to MCU which receive it just fine, I even pass the "cable testing" right there (which is right under the netif_set_up(netif) from previous code example):

while(ethernetif_wait_linkup(&netif, 500) != ERR_OK) {}

But when it comes to sending message back it goes through all the function ending up inside the ip4_route() function when it comes to testing cable connection by the netif_is_link_up(netif_default)) function.

The only documentation about the NETIF_FLAG_LINK_UP is:

If set, the interface has an active link (set by the network interface driver). Either set by the netif driver in its init function (if the link is up at that time) or at a later point once the link comes up (if link detection is supported by the hardware).

So I guess there's something going on with the Netif driver but I can't figure out what it is since I can normally ping and receive any message. Well not entirely, I mean for some reason there's a slight chance that after sending message from PC to MCU the program will crash looking like this:

But this behaviour is as random as my attempts to fix it since sometimes it happens after first message, sometimes it's after 500th message...

I'm using:

IDE: MCUXpresso
SDK: 2.15.00
Board: MIMXRT1170-EVK
MCU: MIMXRT1176

I would appriciate any tips what might cause this behaviour.

Best regards,

Michal.

Re: ENET driver doesn't rise up the NETIF_FLAG_LINK_UP flag

MichalKv — Tue, 19 Mar 2024 07:26:02 GMT

UPDATE #1

So after a while I found out I'm able to rise the flag manually through the netif_set_linkup() function which means I loose the option to automatically notice connected cable but until I somehow find out what's wrong, it's good enough for atleast testing. After rising up the flag manually I'm able to debug and the program seems to be working however the ethernet crashes after some messages (the crash looks like the "Bus Fault" from the original post) but it's often after receiving around 280 messages so it seems like it might be some problem with buffer overflow on my side but I didn't have that much time to find out.

I would still appriciate any tips or info what might cause the NETIF_FLAG_LINK_UP flag not rising up automatically.

Best regards,

Michal.

UPDATE #1.1

I just randomly found that macro LWIP_DHCP_DOES_ACD_CHECK was defined twice - first time in opt.h, second time in lwipopts.h with different values. After fixing that the ethernet seems to be running fine (2000 messages and still going).

The main problem (aka NETIF_FLAG_LINK_UP) still persists.

Best regards,

Michal.

Re: ENET driver doesn't rise up the NETIF_FLAG_LINK_UP flag

Pavel_Hernandez — Tue, 09 Apr 2024 18:41:27 GMT

Hello, sorry for the late response, my name is Pavel, and I will be supporting your case, could you tell me the status of your last message?

Best regard,
Pavel

Re: ENET driver doesn't rise up the NETIF_FLAG_LINK_UP flag

MichalKv — Mon, 15 Apr 2024 06:23:17 GMT

Hello Pavel,

I'm not sure if you're asking about what hapened since last update but if yes I have to say nothing much. I moved to work on other parts of the project since the program is working fine if I rise the flag by myself.

However I'm still curious and I would like to know what causes the behaviour because I haven't noticed anything different from an examples where the "cable connected flag" is being rised automatically just fine. But as I said I haven't notice any more differences and I don't have any other idea where the problem might be.

I thought it might be connected with working on custom board but it's not working even on the MIMXRT1170-EVK kit.

Best regards,

Michal.

Re: ENET driver doesn't rise up the NETIF_FLAG_LINK_UP flag

Pavel_Hernandez — Mon, 15 Apr 2024 17:32:18 GMT

Hello, thanks for your comments, I was asking because your last feedback has been some weeks, let me research more information about this, I will contact you when I have more information.

Best regards,
Pavel

Re: NETIF driver doesn't rise up the NETIF_FLAG_LINK_UP flag

Pavel_Hernandez — Tue, 16 Apr 2024 17:08:49 GMT

Hello, sorry for the late response, I reviewed your information, and I did try the example that you mentioned, but the example works as expected, so I have a question, are you using the RT1170 in a dual-core mode? or could you elaborate further about your application? please.

Best regards,
Pavel

Re: ENET driver doesn't rise up the NETIF_FLAG_LINK_UP flag

Pavel_Hernandez — Tue, 30 Apr 2024 02:07:05 GMT

Hello sorry for the late response I was asking for more information on the internal department, and this is the comments.

You do not need to set NETIF_FLAG_LINK_UP manually.

NETIF_FLAG_LINK_UP reflects if the cable is connected, and this information is from PHY.

When a cable is connected between RT1170 EVK and a PC(Or router), the ENET PHY would detect it.

And then, in the code below, you can see how it works.

So, when cable is plugged out, it would be detected by ENET PHY, and then NETIF_FLAG_LINK_UP would be cleared.

You can verify this idea on EVK.

So, on customer side, if he see this bit is cleared, it is quite possible ENET PHY detected the cabled is plugged out, or is not working well even when it is connected. Customer need to check the PHY status from PHY_GetLinkStatus(), if it is 0, need to check HW connection.

void ethernetif_probe_link(struct netif *netif_) { phy_handle_t *phy = ethernetif_get_phy(netif_); bool status; // true = Link is up status_t st = PHY_GetLinkStatus(phy, &status); if (st == kStatus_Success) { LWIP_ASSERT_CORE_LOCKED(); if (status) { phy_speed_t speed; phy_duplex_t duplex; st = PHY_GetLinkSpeedDuplex(phy, &speed, &duplex); if (st == kStatus_Success) { ethernetif_on_link_up(netif_, speed, duplex); } netif_set_link_up(netif_); } else { netif_set_link_down(netif_); ethernetif_on_link_down(netif_); } } }

Best regards,
Pavel