michi-jung commented on issue #8833:
URL: https://github.com/apache/nuttx/issues/8833#issuecomment-1665163770
Hi @laoniaokkk,
could you please provide your w5500_lower implementation?
Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the
michi-jung commented on issue #8833:
URL: https://github.com/apache/nuttx/issues/8833#issuecomment-1634210413
@laoniaokkk It would be nice to have the
`boards/arm/stm32/stm32f4discovery/ether_w5500` configuration running out of
the box on upstream nuttx. Could you take care of this? I do
michi-jung commented on issue #8833:
URL: https://github.com/apache/nuttx/issues/8833#issuecomment-1634139783
@laoniaokkk Would you be willing to bring your fix upstream?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
michi-jung commented on issue #8833:
URL: https://github.com/apache/nuttx/issues/8833#issuecomment-1633744341
[stm32_exti.h.diff.txt](https://github.com/apache/nuttx/files/12036753/stm32_exti.h.diff.txt)
michi-jung commented on issue #8833:
URL: https://github.com/apache/nuttx/issues/8833#issuecomment-1633606840
@laoniaokkk I believe you are loosing interrupte because of the issue
described
michi-jung commented on issue #8833:
URL: https://github.com/apache/nuttx/issues/8833#issuecomment-1474744785
At the moment I only have board profile for one of my customer's proprietary
boards, which I can not share. I am planning to provide a profile for the
`b-u585i-iot02a` board, but
michi-jung commented on issue #8833:
URL: https://github.com/apache/nuttx/issues/8833#issuecomment-1472477103
The w5500 driver uses the chip in MACRAW mode, i.e. only at the Ethernet
level. All IP processing is done by NuttX's networking stack. This is why
only the MAC is written to a
