Getting IP after some delay (because of monitor_work_handler) on nucleo_h743zi board When using ethernet and zephyr 3.7.1 #96220
Unanswered
ashutoshpandey-eaton
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
phy_log_1 - Copy.log
Issue: Getting Ip after some delay because of phy_mii_initialize() , MII PHY auto-negotiate sequence and monitor_work_handler()
Using On zephyr 3.7.1 with eth_stm32_hal.c
In file phy_mii.c under invoke_link_cb() the callback is coming as NULL, so no callback is called from invoke_link_cb. It seems eth_stm32_hal.c doesnt sets any callback, but monitor_work_handler() runs continuously with frequency of CONFIG_PHY_MONITOR_PERIOD (500ms) **Q1: what is its use in this case? **
Ethernet connect/disconnect is handeled in eth_stm32_hal.c in rx_thread() using net_eth_carrier_on() and net_eth_carrier_off(), Q2: In this case what is the use of phy_mii_initialize and monitor_work_handler() which is running contuinuoulsy ?
If I want to disable the below configs then not able to do because of the dependency present in eth_stm32_hal.c.
CONFIG_PHY_GENERIC_MII=n
CONFIG_ETH_STM32_AUTO_NEGOTIATION_ENABLE=n
If I am commenting the content of monitor_work_handler() getting IP in expected time.
In this case what should I do, If I don't want to upgrade my zephyr 3.7.1 version, but OK to use any patch if required.
Beta Was this translation helpful? Give feedback.
All reactions