- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Original question:
MCU-PLUS-SDK-AM243X: EtherNet/IP Adapter Demos: Link status when auto negotiation fails
I built the demo below and checked its operation.
"ethernetip_adapter_generic_device_mii_demo_am243x-lp_r5fss0-0_freertos_ti-arm-clang"
We checked with version 09.00.00.03 of INDUSTRIAL-COMMUNICATIONS-SDK-AM243X.
I have a question regarding the behavior of the following API.
ETHIP_API uint32_t EI_API_ADP_setModuleNetworkStatusFunc(T* pAdp_p, EI_API_ADP_CBStatus callback_p)
This API allows you to specify a callback function to be called when the Module Status or Network Status changes.
However, the values that can be obtained using the callback function when an IP address has not been obtained are different between DHCP and Bootp.
If an IP address cannot be obtained using DHCP, EI_API_ADP_eSTATUS_LED_ALL_OFF can be obtained for Network Status "net".
However, in the case of Bootp, if the IP address cannot be obtained, EI_API_ADP_eSTATUS_LED_GREEN_BLINK can be obtained for Network Status "net".
I think the correct behavior is for Bootp to be able to obtain EI_API_ADP_eSTATUS_LED_ALL_OFF in the same way as DHCP when an IP address cannot be obtained.
Will it be fixed in the next update?
Hi Nilabh,
In the latest patch, we have confirmed that if an IP address cannot be obtained using BOOTP, the network status "net" of EI_API_ADP_eSTATUS_LED_ALL_OFF can be obtained.
We also confirmed that when the IP address was acquired, the callback function was called and "net" was changed.
I was able to confirm that the issue has been fixed in the test patch.
