Am 24.09.2021 um 13:28 schrieb Marco Giammarini:
> I enabled lwip_stat and print the data every 10 seconds.
> The result is:
> [..]
You have TCP memerr and HEAP err counters != 0, which indicates you are
running out of memory at some point.
That might be due to parallel HTPP connections but I'm n
I enabled lwip_stat and print the data every 10 seconds.
The result is:
TCP
xmit: 16742
recv: 12376
fw: 0
drop: 0
chkerr: 0
lenerr: 0
memerr: 300
rterr: 0
proterr: 0
opterr: 0
err: 0
cacheh
Am 22.09.2021 um 11:38 schrieb Marco Giammarini:
> Dear all,
> in attach you can find new capture.
> The lwip device is: 192.168.1.123 for OSX acquisition, and 192.168.10.123 for
> windows acquisition.
This clearly looks like a memory/configuration problem in lwIP, as (at
least in the windows tra
Sorry, you are right. This acquisition are wrong. I’ll capture new ones.
Regards,
Marco
> Il giorno 20 set 2021, alle ore 12:16, goldsi...@gmx.de ha scritto:
>
> Am 20.09.2021 um 11:54 schrieb goldsi...@gmx.de:
>> Am 20.09.2021 um 11:23 schrieb Marco Giammarini:
>>> In attach you can find two tr
Am 20.09.2021 um 11:54 schrieb goldsi...@gmx.de:
> Am 20.09.2021 um 11:23 schrieb Marco Giammarini:
>> In attach you can find two trace captured with Wireshark. One with Windows,
>> and one with OSX.
>
> There are multiple streams in there. Please explain what we're seeing
> and where you think th
Am 20.09.2021 um 11:23 schrieb Marco Giammarini:
> In attach you can find two trace captured with Wireshark. One with Windows,
> and one with OSX.
There are multiple streams in there. Please explain what we're seeing
and where you think the problem is.
Regards,
Simon
___
Am 17.09.2021 um 10:34 schrieb Tomas Mudrunka:
> Recently there was somebody reporting simillar issue and it turned out
> that some (or most?) browsers use several concurent TCP/HTTP connections
> to load single webpage. Number of these connections was bigger than
> LWIPs default maximum number of
Recently there was somebody reporting simillar issue and it turned out
that some (or most?) browsers use several concurent TCP/HTTP connections
to load single webpage. Number of these connections was bigger than
LWIPs default maximum number of concurent TCP connections, so you might
try to incr
Dear Simon,
Thanks for your reply.
I have set 40kB of heap, and every time I stop the microcontroller in debug
mode during web site request, the free memory is over 70%.
This is my configuration:
#define MEM_SIZE(40*1024)
#define MEMP_NUM_PBUF 28
#define MEMP_NUM_TCP_P
Am 15.09.2021 um 08:55 schrieb Marco Giammarini:
> Dear All,
> I’m studying this problem more in-depth (with Wireshark), and I found
> that sometimes Windows reply with ACK after 40ms at every packet. In
> this case, with a file of 800kB, a packet of 1460B, we have more or less
> 500 packets, that
Dear All,
I’m studying this problem more in-depth (with Wireshark), and I found that
sometimes Windows reply with ACK after 40ms at every packet. In this case, with
a file of 800kB, a packet of 1460B, we have more or less 500 packets, that
multiplied for 40ms reach 20 seconds each file.
I found
Hi all,
I am developing a web server over NXP microcontroller (MK66). It works fine
when the webpage was request by a MAC device or iPhone. The web page was loaded
into 8/10s.
When the device is a Window PC, 3 times out of ten, the web page was loaded
very slowly around 90s and I can’t understan
12 matches
Mail list logo
