lwip-users
[Top][All Lists]
Advanced

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

Re: [lwip-users] freertos + lwip = no uart ?


From: Noam Weissman
Subject: Re: [lwip-users] freertos + lwip = no uart ?
Date: Tue, 28 Jul 2015 19:52:07 +0300

Hi,

The code I placed was just an example.

In any case the RTOS timer interrupt should run at a higher
priority then ETH. The reason is that if you have critical 
section in your code they will not be homered.

Just my two cents input...

BR,
Noam. 


-----Original Message-----
From: address@hidden on behalf of FreeRTOS Info
Sent: Tue 7/28/2015 5:10 PM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] freertos + lwip = no uart ?
 

> I never had problems with UARTS but I did have problems with LwIP when
> interrupts priorities were
>
> not defined properly versus the FreeRTOS interrupt.
>
> 1.

<snip>

As far as I recall the XMega port does not support interrupt nesting, so 
the parameters you highlight are not implemented for that code.

Regards,
Richard.

+ http://www.FreeRTOS.org
Designed for simplicity. More than 113000 downloads in 2014.

+ http://www.FreeRTOS.org/plus
IoT, Trace, Certification, FAT FS, TCP/IP, Training, and more...


_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer 
viruses.
************************************************************************************







************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer 
viruses.
************************************************************************************



<<winmail.dat>>


reply via email to

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