Hi Szabolcs, Not exactly....
I said that TCP stack should be the highest priority because it is doing housekeeping and needs a high time share In order to work properly, and efficiently. Regarding the usage of critical section it is not the preferred or advised way to use LwIP functions outside of the TCP thread context. This is a way I found to be working and gives a solution to some situations. The correct way is to create a call back function and call it from within the TCP stack context. I never used LwIP without an OS running it all so I am not the person to consult with, sorry. I just do not want advise you something I have no experience with :-( Anyone can assist ??? BR, Noam. -----Original Message----- From: lwip-users [mailto:[email protected]] On Behalf Of Vass Szabolcs Sent: Thursday, February 23, 2017 10:15 AM To: Mailing list for lwIP users Subject: Re: [lwip-users] Binary file upload chrashes the program (lwip 1.4.1) Hi Mr. Weissman, Thank You for Your advice. If I understood good, I have to set the ethernet interrupt priority to the highest, and when I use the tcp_write(), or tcp_recved() have to mask all other interrupts? So these are same with mutexes or semaphores under an operating system? And if I didn't use any real time operating system(FreeRTOS) I have to write manually these functions that threat the critical section? Kind regards, Szabolcs Vass 2017.02.14. 10:50 keltezéssel, Noam Weissman írta: > Thank You Mr. Weissman _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
