Hi Prelude, The W5500 initialization code is already merged into mainline:
https://github.com/apache/incubator-nuttx/blob/master/boards/arm/stm32/stm32f4discovery/src/stm32_w5500.c Did you have the chance to test it? BR, Alan On 9/14/22, Alan Carvalho de Assis <acas...@gmail.com> wrote: > Hi Prelude and Michael, > > Yes, I'm adding W5500 to ESP32-S2 to test the SPI driver that I implemented > and because I was facing some issues on it I decided to test on > STM32F4Discovery board. I'll submit the PR to mainline. > > I got it working, but for some reason it is stopping after 5 pings: > https://pastebin.com/raw/8VqpxfMw > > This behavior is consistent, everytime I reset the board it stops after 5th > ping. > > Which board are you planning to use? > > BR, > > Alan > > On Wednesday, September 14, 2022, Michael Jung <michael.j...@secore.ly> > wrote: > >> Hello, >> >> I did implement the w5500 device driver, but I am only using it on a >> proprietary custom board at the moment. Alan is currently working on >> using >> the w5500 with the STM32F4Discovery board. Apparently there are still >> some >> issues, but I guess once those are resolved Alan will upstream the >> respective code. >> >> Bye, >> Michael >> >> On Wed, Sep 14, 2022 at 11:51 AM prelude <wgz_z...@163.com> wrote: >> >> > I saw the driver code of the w5500 on Nuttx, but I did not find any >> > routine using these driver codes. The w5500_initialize interface has >> > not >> > been called by any code. Have any friends used the w5500 on nuttx? >> > >> > >> > int w5500_initialize(FAR struct spi_dev_s *spi_dev, >> > FAR const struct w5500_lower_s *lower, >> > unsigned int devno) >> > { >> > FAR struct w5500_driver_s *self; >> > >> > >> > >> > >> > >> >
