Hello, In my case, there is an additional challenge: the CONFIG_NETINIT_MONITOR is not supported by STM32F4DISCOVERY.
What should I have to do to enable the feature for the board? Best regards, Flavio Em qua., 14 de abr. de 2021 às 10:41, Alan Carvalho de Assis <acas...@gmail.com> escreveu: > > I think this is kind of question that should be in some FAQ or in our > documentation, it is asked often... > > Is there some only place in our Documentation where we could include it? > > BR, > > Alan > > On 4/14/21, Gregory Nutt <spudan...@gmail.com> wrote: > > Normally this is done using the PHY driver at > > nuttx/drivers/net/phy_notify.c that provides PHY-related events to > > applications via signals. It requires board-level support to handle PHY > > interrupts. > > > > The network monitor thread at apps/netutils/netinit (see > > CONFIG_NETINIT_MONITOR) will handle taking the network down if the cable > > is unplugged and bringing it back up when the cable is restored. > > > > On 4/14/2021 7:24 AM, Flavio Castro Alves Filho wrote: > >> Hello, > >> > >> I am implementing an application using NuttX where I need to detect if > >> the network cable is plugged or not in my board. > >> > >> Today I implemented the function netlib_getifstatus(), which automates > >> the read of SIOCGIFFLAGS, similar to what we have in Linux. > >> > >> But, in my tests, it seems that it is not working correctly. > >> > >> What is the recommended approach to have this feature implemented? > >> > >> Best regards, > >> > >> Flavio > >> > > > > -- Flavio de Castro Alves Filho flavio.al...@gmail.com Twitter: http://twitter.com/#!/fraviofii LinkedIn profile: www.linkedin.com/in/flaviocastroalves
