• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 3611 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

lwip tcp abort error

Urvi Shah

Hello, Can any one tell me approx how many free space of RAM does lwip stack required?
LWIP stack is returning me error tcp_abort.

I am using lm3s6965 cortex m-3 processor and the processor has 64KB RAM & 256KB ROM. From that my application has used 50KB of RAM and 175KB of ROM. So is it the problem with memory?

Thanks in advance.

  • 0

    So what have you done to investigate the possible causes of that error?

    What does the LwIP documentation tell you?

    LwIP is Open-Source, so you can look and see what's happening - have you?

    savannah.nongnu.org/.../

    lwip.wikia.com/.../LwIP_Wiki

    lists.nongnu.org/.../lwip-users

  • 0 in reply to Andy Neil

    Thank you, Andrew Neil, for ur response.

    I have referred all the links you have mentioned, and also lots more google link to find solution of my problem.

    Bt i find nothing relevant to my problem. I have also searched on keil's forum. bt there also they have given useful stuff relevant to my problem.

    I have 2 active tcp sockets.
    1. first socket works in tcp_listen mode. at power on this socket gets connected.
    2. second socket works in tcp_connect mode. this socket will try to connect with different tcp client socket one after other on the basis of tcp connection make and break concept.

    I have observed that my tcp_listen socket will be aborted by the lwip stack at random time period. bt my tcp_connect socket works fine.

    So i want to know is there any settings relevant to lwip parameters(MEM_SIZE, PBUF_POOL_BUFSIZE, PBUF_POOL_SIZE, etc...), which i am missing? This al parameters are set to default values given by lwip stack.