Re: [lwip-users] LWIP and System Interrupts

[Jens Nielsen]

Hi Daniel

Glad you're making progress but just to be clear, lwip shouldn't be in crititical section during the entire lwip_send sequence, that is only used for short code sections. What you might be looking at (depending on your settings) is LWIP_TCPIP_CORE_LOCKING and LOCK_TCPIP_CORE/sys_mutex_lock which should just take a mutex and not block your interrupts.

Best regards
Jens

On 2018-06-09 18:06, Daniel Sexton wrote:

Jens,

Thank you for the quick response. I have indeed tracked it down to the EntertaskCritical & ExitTaskCritical system calls.

Although I do have the Max Syscall Interrupt Priority set correctly it appears that it is blocking all interrupts, not just those set at a priority equal to or lower than the max (Max is 5 and my interrupts are set to 0). They should be working. In addition, since the task critical functions keep track of nesting my interrupt does not start firing again until the LWIP operation is completed, in the case I measured which was an lwip_send, it took 120msec. I will now look elsewhere for a solution to this problem, I am sure there is a configuration setting I am missing somewhere.

 

Daniel Sexton