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

[Noam Weissman]

Hi,

I think that RAW API without OS could work fine. Define 3-4K RAM for LwIP 
memory pool. 
Define MSS size 516 or even less.. maybe 256 bytes with a window of 3 * MSS...

I have no experience with XMEGA I am just guessing ...

Good luck,
Noam.


-----Original Message-----
From: address@hidden on behalf of unnamed
Sent: Tue 7/28/2015 9:25 PM
To: address@hidden
Subject: Re: [lwip-users] freertos + lwip = no uart ?
 
hmm rtos is running at higher priority than lwip so i think thats not it. but i 
wonder if it's relevant ? i don't use lwip right now, i just compile it into my 
project, but no lwip_init() is called. i dont include any .h files right now in 
my main.c or other project files.

task with test printf() have also blinking led and vTaskDelay() - led blinks 
but no message from uart.


but maybe it's just about 8kb of ram ? i didn't found anywhere about minimal 
requirements and after seeing project called lwip-avr (or something like that) 
i thought that it should run on xmega - right now i think that's what's wrong 
with my application.

raw lwip without os should work on my chip ?




2015-07-28 18:27 GMT+02:00 Noam weissman [via lwIP] <[hidden email]>:


        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: lwip-users-bounces+noam=[hidden email] 
<http:///user/SendEmail.jtp?type=node&node=24739&i=0>  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 
        [hidden email] <http:///user/SendEmail.jtp?type=node&node=24739&i=1>  
        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. 
        
************************************************************************************
 
        
        
        
        
        _______________________________________________ 
        lwip-users mailing list 
        [hidden email] <http:///user/SendEmail.jtp?type=node&node=24739&i=2>  
        https://lists.nongnu.org/mailman/listinfo/lwip-users

         <http://lwip.100.n7.nabble.com/images/icon_attachment.gif> winmail.dat 
(5K) Download Attachment 
<http://lwip.100.n7.nabble.com/attachment/24739/0/winmail.dat> 


________________________________

                If you reply to this email, your message will be added to the 
discussion below:
        http://lwip.100.n7.nabble.com/freertos-lwip-no-uart-tp24724p24739.html 
        To unsubscribe from freertos + lwip = no uart ?, click here.
        NAML 
<http://lwip.100.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
  



________________________________

View this message in context: Re: freertos + lwip = no uart ? 
<http://lwip.100.n7.nabble.com/freertos-lwip-no-uart-tp24724p24740.html> 
Sent from the lwip-users mailing list archive 
<http://lwip.100.n7.nabble.com/lwip-users-f3.html>  at Nabble.com.



************************************************************************************
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>>