lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] lwip-users Digest, Vol 227, Issue 7


From: Peter
Subject: Re: [lwip-users] lwip-users Digest, Vol 227, Issue 7
Date: Thu, 14 Jul 2022 07:21:56 +0100

I have solved the LWIP_TCPIP_CORE_LOCKING=1 issue.

Details here
https://www.eevblog.com/forum/microcontrollers/any-stm-32f4-eth-lwip-freertos-mbedtls-experts-here-(not-free-advice)/msg4298761/#msg4298761

It was overlapping mutex regions, due to incorrect code in
ethernetif.c.

The MEMP_MEM_MALLOC=1 issue remains unresolved but I don't need it. It
seems "neater" but is doesn't generate RAM from nowhere...

Peter



>Send lwip-users mailing list submissions to
>       lwip-users@nongnu.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>       https://lists.nongnu.org/mailman/listinfo/lwip-users
>or, via email, send a message with subject or body 'help' to
>       lwip-users-request@nongnu.org
>
>You can reach the person managing the list at
>       lwip-users-owner@nongnu.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of lwip-users digest..."
>
>
>Today's Topics:
>
>   1. Re: How to use LWIP from FreeRTOS tasks - a thread safety
>      question (Peter)
>   2. Re: How to use LWIP from FreeRTOS tasks - a thread safety
>      question (Jeffrey A. Wormsley)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue, 12 Jul 2022 17:17:22 +0100
>From: Peter <peter@peter2000.co.uk>
>To: Dave Nadler <drn@nadler.com>
>Cc: Mailing list for lwIP users <lwip-users@nongnu.org>
>Subject: Re: [lwip-users] How to use LWIP from FreeRTOS tasks - a
>       thread safety question
>Message-ID: <202207121617.26CGHNS3094625@mail.authsmtp.com>
>Content-Type: text/plain; charset=us-ascii
>
>
>
>>Hi Peter - Can you start at the beginning?
>>Has this ever worked, or for 2 years it always crashed if you used LWIP?
>>What exactly "crashes the whole thing"?
>>You're aware of the numerous issues surrounding STM-provided Ethernet 
>>driver?
>>Hope this helps,
>>Best Regards, Dave
>
>I have spent more time on that LWIP_TCPIP_CORE_LOCKING=1 issue.
>Tracing through the code, it does appear that eventually LWIP does end
>up using FreeRTOS mutexes.
>
>It breaks something else however, and I can't easily trace it because
>DHCP fails to work, and one can't really trace that because taking a
>breakpoint causes timeouts etc. Also that code is too convoluted for
>me to understand :)
>
>I have been trying to find advice around the place and this post
>summarises my latest findings on this
>
>https://www.eevblog.com/forum/microcontrollers/lwip-32f417-how-to-optimise-network-stack-memory-allocation/msg4295431/#msg4295431
>
>
>
>------------------------------
>
>Message: 2
>Date: Tue, 12 Jul 2022 13:50:21 -0400
>From: "Jeffrey A. Wormsley" <daworm@gmail.com>
>To: Mailing list for lwIP users <lwip-users@nongnu.org>
>Cc: Dave Nadler <drn@nadler.com>
>Subject: Re: [lwip-users] How to use LWIP from FreeRTOS tasks - a
>       thread safety question
>Message-ID:
>       <CAF6o3h-+GP6vTSj-9EpZUbup0v959ehEa=4VPGw6CSHkqrQn0g@mail.gmail.com>
>Content-Type: text/plain; charset="utf-8"
>
>No real help here, but that CMSIS layer is intended to let you write your
>application to one API, then port it to multiple RTOSes or even full
>desktop/server OSes, presumably without changes.  And digging through that
>code is always (read "never") fun.
>
>Jeff
>
>On Tue, Jul 12, 2022 at 12:18 PM Peter <peter@peter2000.co.uk> wrote:
>
>>
>>
>> >Hi Peter - Can you start at the beginning?
>> >Has this ever worked, or for 2 years it always crashed if you used LWIP?
>> >What exactly "crashes the whole thing"?
>> >You're aware of the numerous issues surrounding STM-provided Ethernet
>> >driver?
>> >Hope this helps,
>> >Best Regards, Dave
>>
>> I have spent more time on that LWIP_TCPIP_CORE_LOCKING=1 issue.
>> Tracing through the code, it does appear that eventually LWIP does end
>> up using FreeRTOS mutexes.
>>
>> It breaks something else however, and I can't easily trace it because
>> DHCP fails to work, and one can't really trace that because taking a
>> breakpoint causes timeouts etc. Also that code is too convoluted for
>> me to understand :)
>>
>> I have been trying to find advice around the place and this post
>> summarises my latest findings on this
>>
>>
>> https://www.eevblog.com/forum/microcontrollers/lwip-32f417-how-to-optimise-network-stack-memory-allocation/msg4295431/#msg4295431
>>
>> _______________________________________________
>> lwip-users mailing list
>> lwip-users@nongnu.org
>> https://lists.nongnu.org/mailman/listinfo/lwip-users
>>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: 
><https://lists.nongnu.org/archive/html/lwip-users/attachments/20220712/e1a0f157/attachment.htm>
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>lwip-users mailing list
>lwip-users@nongnu.org
>https://lists.nongnu.org/mailman/listinfo/lwip-users
>
>
>------------------------------
>
>End of lwip-users Digest, Vol 227, Issue 7
>******************************************



reply via email to

[Prev in Thread] Current Thread [Next in Thread]