Thanks again!!!! is perfect to wait for data regards Oscar
On Fri, Sep 4, 2009 at 1:51 PM, Mathias Zenger <[email protected]>wrote: > The way I am using select() the task will block. Meanwhile the scheduler > will continue running other tasks. No starvation will happen. > As soon as incoming data arrives the task will become "ready" and the > scheduler will run it at next occasion. > > > > > -----Ursprüngliche Nachricht----- > *Von:* [email protected] [mailto: > lwip-users-bounces+m.zenger <lwip-users-bounces%2Bm.zenger>=mobatime.com@ > nongnu.org]*Im Auftrag von *Oscar F > *Gesendet:* Freitag, 4. September 2009 13:34 > *An:* Mailing list for lwIP users > *Betreff:* Re: [lwip-users] help with socket!! > > Another question, if the protocol is TCP, can i use lwip_select to block > the task to wait for a data? > > if the task is blocked, the other task in the system can be runned? > > thank again > Oscar > > On Fri, Sep 4, 2009 at 1:24 PM, Oscar F <[email protected]> wrote: > >> Thanks Mathias, i´ll see your file. I don´t know the protocol because >> i´ve readed the customer documentation and it doesn´t say anything about >> protocol. >> " >> >> links connection process shall be initiated by the PC unit: it will >> connect sequentially (one after the other) all the logical links. >> >> At power-on/reset, the EVK-1100 Unit shall first create the sockets in >> order to be ready for accepting a connection in all of them." >> >> >> the connection are permanent maybe will be TCP no? because then there is a >> diconnect process. >> >> >> i´ll need 8 socket TCP connection permanent , do you think the same? >> >> >> Regards >> >> Oscar >> >> >> >> >> On Fri, Sep 4, 2009 at 1:04 PM, Mathias Zenger >> <[email protected]>wrote: >> >>> What protocol do you use UDP or TCP? I just implemented a task for >>> the same system (EVK1100/FreeRTOS/lwIP). It receives UDP datagrams from a >>> multicast address on different ports. I attached the file to show you how >>> select() can be used. For answering the requests you could write a second >>> task which gets woken by the receiver task (e.g. use queues to signalize the >>> request). >>> >>> Regards, Mathias >>> >>> >>> >>> -----Ursprüngliche Nachricht----- >>> *Von:* [email protected] [mailto: >>> lwip-users-bounces+m.zenger <lwip-users-bounces%2Bm.zenger>=mobatime.com >>> @nongnu.org]*Im Auftrag von *Oscar F >>> *Gesendet:* Freitag, 4. September 2009 12:28 >>> *An:* Mailing list for lwIP users >>> *Betreff:* [lwip-users] help with socket!! >>> >>> Hello everybody, my customer said me that i need to create 8 socket of >>> communication with diferent port. >>> >>> There will be 8 logical links with a Port number associated: >>> >>> >>> >>> - RQ1 Port Number = 1500H (= >>> 6376 dec) >>> >>> - RQ2 Port Number = 1501H (= >>> 6377 dec) >>> >>> - RQ3 Port Number = 1502H (= >>> 6378 dec) >>> >>> >>> >>> - RP1- Port Number = 1600H >>> (= 6632 dec) >>> >>> - RP2-Port Number = 1601H (= >>> 6633 dec) >>> >>> - RP3-Port Number = 1602H (= >>> 6634 dec) >>> >>> - RP4-Port Number = 1603H (= >>> 6635 dec) >>> >>> - RP5-Port Number = 1604H (= >>> 6636 dec) >>> >>> >>> Each answer and request goes form diferent socket. >>> >>> >>> I have the evk1100 with avr32, and i use the lwip 1.3.0 with free RTOS >>> port to this micro. >>> >>> >>> Can i create 8 socket, and wait for request of them and answed for other >>> ? >>> >>> >>> in the program run other task, do you recommended use the lwip_select >>> function to block for request, and the task state will be blocked and other >>> task can be runned? >>> >>> >>> Thank you for all >>> >>> Regards >>> >>> Oscar >>> >>> >>> _______________________________________________ >>> lwip-users mailing list >>> [email protected] >>> http://lists.nongnu.org/mailman/listinfo/lwip-users >>> >> >> > > _______________________________________________ > lwip-users mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
