Replies: 3 comments 2 replies
-
I'm traveling so can't find the exact PR, but if you look at the merged PR that added wired Ethernet you'll see the discussion about this. The core uses native LWIP and a polled architecture. You can manually adjust the polling frequency by editing a constant, described there. It should be possible to implement an IRQ based setup with some work. There is also probably support for multiple packets per notification when using the cooked stack in the W5100 chip. Not sure if that's possible in raw Ethernet mode which is what running LWIP needs. |
Beta Was this translation helpful? Give feedback.
-
I think you mean this one right? To understand it correctly: Is this polling in a timer interrupt or is it in the main loop ? The problem is, I see quite big delays (often in range of 5-20ms, less often up to 100ms) when using wired ethernet. |
Beta Was this translation helpful? Give feedback.
-
ah now.. It is about a blocked main loop. I'll try to track this down further. But maybe you have some idea or hint for me. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I moved my project from "Ethernet_Generic" stack to the core's lwip_w5500 implementation.
I recognized some behaviour that I did not expect and I did not experience before with the Ethernet_Generic stack (application more or the less unchnanged).
My application sends (udp.begin, write, end) and receives (udp.read) data.
I monitor my loop timings closely to ensure my response time.
There are quite often some delays > 10ms, but also some delays from about 50-100ms in rare cases.
These delays occour in functions that cannot be the cause, so I assume that maybe interrupts cause this.
Is that possible?
Beta Was this translation helpful? Give feedback.
All reactions