On 05.07.2018 16:18, Nenad Pekez wrote:
[..]
I don't think any calls to lwIP are made from an ISR.
Yes, that looks good so far from what you wrote. I'm afraid I don't have
any more ideas now. You'll have to try and debug it yourself. E.g. set a
breakpoint at when the stats underflow happens.
And from which context are timers processed?
Xilinx timers are used. Each 250ms timer callback is called inside which
TcpFastTmrFlag (for 250ms) and/or TcpSlowTmrFlag (for 500ms) variables
are set to 1. In the main loop, there is this:
while (1) {
if (TcpFastTmrFlag) {
Nenad Pekez wrote:
> I took a look at this. This has been provided by Xilinx drivers already.
> In their MAC receive handler they allocate memory for pbuf (call to
> pbuf_realloc() actually) and enqueue it. In the main loop, I call Xilinx
> function xemacif_input() which check if there is anythi
Have you read this:
http://www.nongnu.org/lwip/2_0_x/pitfalls.html
I took a look at this. This has been provided by Xilinx drivers already.
In their MAC receive handler they allocate memory for pbuf (call to
pbuf_realloc() actually) and enqueue it. In the main loop, I call Xilinx
function xema
I have ATSAME MCU and ESP32.
I used ready to use esp-idf examples to create tcpip client in eclipse with
ESP32(standalone) and its working great.
Now, I want to make a tcp_client using ESP32 module together with ATSAME53.
ATSAME will be acting as the main MCU and I want to create a client using
Nenad Pekez wrote:
> > Have you checked the stats if you run out of memory somewhere?
> I have checked them, and there is certainly something wrong. After some
> time, stats for memory seem to overflow, at least that's my impression.
>
> At one point I have this:
> MEM HEAP
> avail: 6
>
Hi Simon,
But it seems irrelevant?
Yes, it's irrelevant.
Have you checked the stats if you run out of memory somewhere?
I have checked them, and there is certainly something wrong. After some
time, stats for memory seem to overflow, at least that's my impression.
At one point I have this:
