lwip users (embeddable IP stack)

headers Laconsults | 1 Oct 2005 21:43

_______________________________________________
lwip-devel mailing list
lwip-devel <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/lwip-devel

_______________________________________________
lwip-users mailing list
lwip-users@...
http://lists.nongnu.org/mailman/listinfo/lwip-users
Good evening,

I am working on an embedded MMS project with modem and
PPP support.
I am using lwip1.1.0 stack.
I have several problems when receiving files bigger
than 3 KBytes.
The socket is often blocking to get data so i wonder
if the socket select management is right.

Does anybody know how to manage fd_sets building
before running select, for a non UNIX OS ?
ie is it necessary to use FD_ZERO, FD_SET, FD_ISSET
like commands on real-time OS ?

Thanks in advance and regards,

Vincent BRUYERE

___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

kyle treleaven wrote:
> Hi all,
> 
> I'm trying to use the Xilinx-provided port of lwIP on a PPC405
> (embedded) running the "standalone" OS-- ie. no OS.  I'm using the raw
> API, and I've simply compiled a bit of tutorial code (a small echo
> server) provided in an appnote by Xilinx-- I'm sure a lot of people
> have run the same drill.  But for some reason my compiles keep running
> up in the 800K range, which is way way way too big for my poor little
> fpga.  Plus it seems ridiculous when compared to the "tens of
> kilobytes" that everybody else claims on other platforms.  My mem/memp
> settings are (the defaults):
> 
> MEM_SIZE: 8192
> MEMP_NUM_PBUF: 16
> MEMP_NUM_UDP_PCB: 5
> MEMP_NUM_TCP_PCB: 5
> MEMP_NUM_TCP_PCB_LISTEN: 5
> MEMP_NUM_TCP_SEG: 255
> 
> I'm under the impression that these are the only settings that matter
> for raw api use.
> 
> Has anybody else had this problem? Anybody know what's going on?

What kind of executable are you compiling?
(is it an executable? or is it some kind of ROM image, or FPGA image?)

If possible, try to convince the linker to create a map file for you.
The map file should tell you exactly where the memory is going.

All the best,
Bertrik

On Tuesday 04 October 2005 19:39, Vincent Bruyere wrote:
> Good evening,
>
> I am working on an embedded MMS project with modem and
> PPP support.
> I am using lwip1.1.0 stack.
> I have several problems when receiving files bigger
> than 3 KBytes.
> The socket is often blocking to get data so i wonder
> if the socket select management is right.
>
> Does anybody know how to manage fd_sets building
> before running select, for a non UNIX OS ?
> ie is it necessary to use FD_ZERO, FD_SET, FD_ISSET
> like commands on real-time OS ?

lwIP sockets work just like UNIX sockets. That means that you should manage 
fd_sets just like you would on UNIX environment.

	- Atte

ok Atte, thanks for your answer.
But as far as I know, the 'select' use is usefull on
the server side to avoid creating one process per
socket.
Is the 'select' routine necessary on the client side ?

Vincent

--- Atte Kojo <atte.kojo@...> a écrit :

> On Tuesday 04 October 2005 19:39, Vincent Bruyere
> wrote:
> > Good evening,
> >
> > I am working on an embedded MMS project with modem
> and
> > PPP support.
> > I am using lwip1.1.0 stack.
> > I have several problems when receiving files
> bigger
> > than 3 KBytes.
> > The socket is often blocking to get data so i
> wonder
> > if the socket select management is right.
> >
> > Does anybody know how to manage fd_sets building
> > before running select, for a non UNIX OS ?
> > ie is it necessary to use FD_ZERO, FD_SET,
> FD_ISSET
> > like commands on real-time OS ?
> 
> lwIP sockets work just like UNIX sockets. That means
> that you should manage 
> fd_sets just like you would on UNIX environment.
> 
> 	- Atte
> 
> 
> _______________________________________________
> lwip-users mailing list
> lwip-users@...
> http://lists.nongnu.org/mailman/listinfo/lwip-users
> 

___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

_______________________________________________
lwip-users mailing list
lwip-users@...
http://lists.nongnu.org/mailman/listinfo/lwip-users

lwip-users-bounces+christiaan.simons=axon.tv@... wrote
on 10-10-2005
11:34:25:

>          I already posted lot of questions to this group regarding
> my tftp client implementation of lwip , but I did not get any
> replies .I also posted my source code implementation , but the same.

Posting code doesn't make the coders actually look at it,
most of us dislike that. If you want implementation support
you should be more specific than 'it doesn't work' and describe
the problem in text please.

> I hope you can guide me with my probelm this time . As I said I am
> writing a tftp client application on lwip using the socket API ,
> tapif interface (using bridge configuration ) on Redhat linux 2.4.
> 20-8 . I need to put and get files from/ to a remote server. But
> both   put and get are not working.While getting I am only getting
> first 512 bytes and then tapif_input function halts

Ah this is better,
As far as I can remember the TFTP protocol uses a state-machine.
Can you tell us in which state the server is? And can you make
the state transitions visible?

Tapif_input will repeatedly be called for the incoming TFTP datagrams,
most likely causing server state changes.

> I am creating
> only 1 thread in my application and I guess this is making problems

Please do not guess, do you know whats actually going on in the code?

If there are multiple threads in the design you shouldn't remove
or disable them. What are these threads for?

> , How can I use thread mechanism safely in my application ??? I am
> herewith attaching my implementation to this email , please have a
> look and suggest me in this ...Help!!!!!!!
>
>
>  Also one more thing is I profile my whole stack using gprof
> /Functioncheck (profiling tools on linux ) as a part of my work ,
> these tools are giving erroneous(wrong) results  for example
> sys_arch_sem_wait is called 744 times , sys_sem_signal is called 699
> times ...and so on.... do u guys really think that these functions
> are called this many number of times.... I run my application and
> then run the tool , so it is a dynamic execution profiler.....I
> guess there is a problem with my thread implementation....

Ah, do not use gprof. For another project a colluege of mine
crippled some code by adding profiling flags to a Makefile.

It took me a week to find the root-cause.

Sorry, I'm not going to look at your code for now.

Christiaan Simons

Hardware / Software Engineer
Axon Digital Design

+31 (0)13 511 66 66
+31 (0)13 511 41 51

christiaan.simons@...
http://www.axon.tv

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named.  If you are not the named addressee you should not
disseminate, distribute or copy this e-mail.

_______________________________________________
lwip-users mailing list
lwip-users@...
http://lists.nongnu.org/mailman/listinfo/lwip-users

>      I use the TFTP server from the linux system , not from the lwip
> .While getting a file from the remote server,  I can observe the
> first 512 bytes (which tftp server has to send ) on my client side ,
> using ethereal , but as I said  tapif_input halts after some time ,
> I thought it would be the problem from my TFTP client timeout
> mechanism , so I increased the timeout of my TFTP client , no change.

Ah, thus the TFTP client runs on top of lwip.

Does the server get a proper ACK from the client, in time?
The timeout of your server can play a major role here.

>      I created only a single thread , there are no multiple threads
> , I saw in one of the lwip message list that we should create a new
> thread for sending and receiving , I do not know about my
> application , whether to use multiple threads . I have no idea of
> threading  , So I asked for an explanation of the thread mechanism
> which can be used safely in our applications,

There are 2 examples in the contrib/ports/unix tree.
The 'simhost' example uses the netconn/socket api which you
probably use. Follow this as a reference.

>     Gprof , is ok with normal applications , but it has problems
> with threaded applications on Linux ,  Can we write an application
> on lwip  with out threading ...?`?? If so how can we do this...?

I just recommend not to use it.
Profiling won't help solving this issue anyway.

>   Please see the code when you find some time....
No.

Bye,

Christiaan Simons

Hardware / Software Engineer
Axon Digital Design

+31 (0)13 511 66 66
+31 (0)13 511 41 51

christiaan.simons@...
http://www.axon.tv

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named.  If you are not the named addressee you should not
disseminate, distribute or copy this e-mail.

Mon	Tue	Wed	Thu	Fri	Sat	Sun

					1	2
3	4	5	6	7	8	9
10	11	12	13	14	15	16
17	18	19	20	21	22	23
24	25	26	27	28	29	30
31

37	May 2013
60	April 2013
71	March 2013
85	February 2013
111	January 2013
98	December 2012
73	November 2012
48	October 2012
97	September 2012
184	August 2012
137	July 2012
186	June 2012
197	May 2012
54	April 2012
125	March 2012
157	February 2012
123	January 2012
86	December 2011
173	November 2011
130	October 2011
275	September 2011
169	August 2011
149	July 2011
110	June 2011
171	May 2011
184	April 2011
163	March 2011
80	February 2011
49	January 2011
105	December 2010
151	November 2010
173	October 2010
105	September 2010
120	August 2010
102	July 2010
111	June 2010
139	May 2010
152	April 2010
231	March 2010
230	February 2010
175	January 2010
91	December 2009
108	November 2009
213	October 2009
232	September 2009
241	August 2009
271	July 2009
178	June 2009
134	May 2009
171	April 2009
214	March 2009
162	February 2009
119	January 2009
138	December 2008
155	November 2008
159	October 2008
128	September 2008
177	August 2008
107	July 2008
47	June 2008
162	May 2008
126	April 2008
185	March 2008
170	February 2008
234	January 2008
138	December 2007
168	November 2007
147	October 2007
177	September 2007
70	August 2007
126	July 2007
155	June 2007
189	May 2007
133	April 2007
239	March 2007
164	February 2007
55	January 2007
52	December 2006
62	November 2006
167	October 2006
142	September 2006
91	August 2006
82	July 2006
54	June 2006
71	May 2006
95	April 2006
98	March 2006
40	February 2006
60	January 2006
77	December 2005
92	November 2005
49	October 2005
45	September 2005
73	August 2005
48	July 2005
70	June 2005
41	May 2005
37	April 2005
41	March 2005
70	February 2005
86	January 2005
109	December 2004
113	November 2004
105	October 2004
126	September 2004
91	August 2004
125	July 2004
109	June 2004
44	May 2004
1	October 2001
1	January 2000

Re: FREE LICENSE BUNDLING Historic Significant Next Generation TCP onto IwIP ...

Re: lwip memory on a xilinx ml403 dev board

fd_sets building

Re: lwip memory on a xilinx ml403 dev board

Re: fd_sets building

Re: fd_sets building

[lwip users] using threads in our application safely ???

Re: [lwip users] using threads in our application safely ???

Re: [lwip users] using threads in our application safely ???

Re: [lwip users] using threads in our application safely ???