LWIP Memory options question
I have been using LWIP on a Stellaris CPU with TI's code Composer Studio and
have had it working for some time but I have some questions about tuning it
for RAM usage. I have plenty of code space but limited RAM (96K RAM) total.
The application is using LWIP only for
I am using lwip on a stellaris micro that is running safeRTOS. I have three
TCP/IP sockets I use to send and receive data. One socket sends 10k bytes
and the other two sockets send and receive data in 256 byte blocks at a
time. When I increased the size of the data I send from 6k bytes to 10K
by
Thanks Simon! The files weren't part of my distribution, I found them on
the download sight " http://download.savannah.gnu.org/releases/lwip/";. I'll
give it a try and see if it works.
Thanks,
DB
>
> "shogun" wrote:
> > I didn't
> > se
I am using the RAW API of lwip version 1.3.2 on a Stellaris CPU. I would
like to ping the network device (PC) on the other end of the cable. I didn't
see anything in the API to do a ping to another IP. Is this supported and
if so how would I do it?
Thanks,
DB
___
I have one more question about what is safe to run in different execution
context for lwip (interrupt/thread). I did add an OS to my application and
now moved some things around so data is only sent and received in the tcp/ip
thread context. Is it recommended I move any of the following API calls
>
>
> "shogun" wrote:
> > I have a general question about choosing the correct API to use for
lwip.
> > Is the RAW API typically used without an OS and the netcomm and BSD API
> > typically used with an RTOS?
>
> Not necessarily: netconn- and socke
I have a general question about choosing the correct API to use for lwip.
Is the RAW API typically used without an OS and the netcomm and BSD API
typically used with an RTOS? I know there are probably many ways to make
something work and I'm not looking to make more work than needed but I am
not
Kieran,
I was working on this over the weekend but could not test it at home without
the right equipment so I wanted to understand it as much as I could. I used
the tcpip_callback to indicate to main (in my case without an OS yet) and
did all the processing of the data in main. As part of the mai
: text/plain; charset=us-ascii
>
>
> On 28 Nov 2010, at 15:37, shogun wrote:
>
> > Since the document is out of date, what
> > should I be reading and using for a reference to help me understand this
to
> > select the right API and implement it correctly?
>
&g
I have been trying to better understand LWIP and looking for help and or
documentation to help me understand LWIP better. I am using a Stellaris CPU
from TI and been using the RAW API without an OS using lwip version 1.3.1
and just using the callbacks to receive data and tcp_write() to send data.
>
>Message: 3
>Date: Wed, 24 Nov 2010 22:00:51 +0100
>From: "goldsi...@gmx.de"
>Subject: Re: [lwip-users] Re: another reentrancy question
>To: Mailing list for lwIP users
>Message-ID: <4ced7d03.7030...@gmx.de>
>Content-Type: text/plain; charset=ISO-8859-
>Am 23.11.2010 um 03:19 schrieb "shogun" :
>
>> . Every time I stop it and
>> it is not working properly, it is in the file tcp_in.c, the function
>> tcp_input() and going between the two source lines below only:
>>
>> (line 180) for(pcb =
"shogun" wrote
> If you are running lwip without an OS, I am not clear on how this can be
> prevented if it is a problem. If the main application can send data via a
> socket
That cannot happen: our sockets need an OS, so you won't have sockets
running without an
This is from September 7th
Question back then:
> On another note, what do I have to be careful of in regards to lwip not
> being reentrant?
Answer back then:
If you are using the sockets or netconn API, don't use the same socket or
netconn from multiple threads. If you are using the raw API, d
On 3 Sep 2010, at 23:49, shogun wrote:
> Can someone tell me if this is a reentrancy issue? If I send data too
fast
> on a socket and the stack is still sending the data and I make another
call
> to send more data, will that cause a problem?
It's not clear from your email wh
Can someone tell me if this is a reentrancy issue? If I send data too fast
on a socket and the stack is still sending the data and I make another call
to send more data, will that cause a problem?
I am using a Stellaris 9b92 CPU running 80 MHz using lwip to send TCPIP data
on a server socket. Th
On Thu, 2010-08-19 at 17:36 -0400, shogun wrote:
> I have some extra stuff I more or less removed in the structure
> "mainNetInfoStruct" but ignore that. mainNetInfoStruct does however
> contain
> the pointer to the PCB in the accept callback to be used later for
> s
This all seems a little confused. You're trying to close a data PCB but
then to re-open it you're creating a listening PCB. Do you not still
have the bound listening PCB from when you first accepted the
connection? You should be able to just call tcp_accept() on that to
re-open the data socket
I have a couple questions about getting an error on tcp_write() using lwip.
Sometimes I get an (0xFF) error from the send function:
//this is sudo code here
ert = tcp_write(my_pcb, data, size, 0);
if(ert)
{
close_socket()
}
I do not yet know if the error is on the embedded lwip side
All,
Thanks for the help on this one
I do have one more question. What do you recommend to clean up after a
error on a socket?
I was doing something like this and it seemed to work but I do not know what
is recommended.
static void close_socket(struct tcp_pcb *pcb)
{
tcp_arg(pcb, N
Thanks for the help it is working much better now! The comments about
freeing memory is from this thread:
http://e2e.ti.com/support/microcontrollers/stellaris_arm_cortex-m3_microcont
roller/f/471/p/54250/192785.aspx#192785
How do you recommend I free the memory?
21 matches
Mail list logo
