|
From: | Noam Weissman |
Subject: | Re: [lwip-users] LWIP_MPU_COMPATIBLE set to 1, but still get memory management fault in lwip_select. |
Date: | Wed, 6 Sep 2017 21:33:16 +0000 |
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...
Works like a charm. BR, Noam. From: lwip-users <lwip-users-bounces+address@hidden> on behalf of David Lockyer <address@hidden>
Sent: Wednesday, September 6, 2017 5:12 PM To: address@hidden Subject: [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 LWIP_MPU_COMPATIBLE define, so a direct modification of the stack source was not required. However for me it still appears to try to access another threads memory, triggering an exception. The changes I had to make were: Index: lib/lwip-2.0.2/src/api/sockets.c Is there something else I missed here that would remove the need for this modification?
Kind regards, David Lockyer ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ |
[Prev in Thread] | Current Thread | [Next in Thread] |