Re: [lwip-users] LWIP_MPU_COMPATIBLE set to 1, but still get memory management fault in lwip_select.

Hi David, I have upgraded LwIP from 1.41 to 2.02 and only handled the sys_arch.h/c files The only thing I can remember that I had to change was the ip_addr variable definitions in my own code. Beside that I have not mad any change to the LwIP code. STM32F4 and also F7 with FreeRTOS...

Re: [lwip-users] malloc limitation

On Wed, Sep 6, 2017 at 3:26 PM, Patrick Klos wrote: > On 9/6/2017 1:55 AM, Ran Shalit wrote: >> >> Hello, >> >> I porting lwip into uc/os, but noticed that lwip use malloc() >> operation, and I have limitation with this OS, thet malloc is limited >> to 4045. > > > Is that 4045

[lwip-users] Received packets thread

Hello, Our Ethernet driver does not provide interrupt, and can only use polling. I though that I can use rx thread as part of the threads created with sys_thread_new. But I am not sure about its priority related to tcpip thread , and the rate for polling if there is new received packet. Is

[lwip-users] LWIP_MPU_COMPATIBLE set to 1, but still get memory management fault in lwip_select.

Hi, I have a project that uses an STM32F MCU running FreeRTOS (cortex mpu port) & lwip, with the MPU enabled. I'm upgrading to lwip 2.0.2 from lwip 1.4.1, that I had to customize to be compatible with the MPU, in particular in lwip_select(). The motivation was to use the

Re: [lwip-users] IPv6 MTU vs IPv4 MTU

Raphael Zulliger wrote: I'd like to stress again that both, the mentioned Ubuntu and a Windows 10 system respect different MTUs for IPv4 and IPv6 That was clear from the first mail. Maybe it got clear from my mail, that I wanted to know what are the downsides of our behaviour. I failed to

Re: [lwip-users] IPv6 MTU vs IPv4 MTU

Thanks for your replies. I'd like to stress again that both, the mentioned Ubuntu and a Windows 10 system respect different MTUs for IPv4 and IPv6 in my case, as shown by Wireshark. I.e. Sending UDP frames, it behaves like this: - IPv4: Frames are being fragmented starting from 1473 Bytes

Re: [lwip-users] malloc limitation

On 9/6/2017 1:55 AM, Ran Shalit wrote: Hello, I porting lwip into uc/os, but noticed that lwip use malloc() operation, and I have limitation with this OS, thet malloc is limited to 4045. Is that 4045 bytes max per allocation?  Or 4045 bytes total allocatable space? Does it mean that it