lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] TFTP init


From: contact
Subject: Re: [lwip-users] TFTP init
Date: Wed, 18 Jan 2017 20:10:58 +0530

I guess you need to check memory configuration. How much RAM do you have? Are you using memory pool or malloc?

One thing to note here, I have written modified vfs layer for both my systems as none of them use FatFS. I don’t know if that will have any impact as such. You better check your lwIP options for memory settings.

 

  • Ajay B.

 

From: nrichard
Sent: Wednesday, January 18, 2017 7:39 PM
To: address@hidden
Subject: Re: [lwip-users] TFTP init

 

Ajay Bhargav wrote

> I am using this FTP server on two of my devices (ARM board and ESP8266)

> and it works perfectly fine. Can you enable FTP debug prints and see where

> exactly it is failing?

>

> Regards,

> Ajay Bhargav

 

I turned on TCP as well as FTP debugging, and low and behold, it tells me

I'm out of memory...

 

/TCP header:

+-------------------------------+

|    22271      |       21      | (src port, dest port)

+-------------------------------+

|           0032031823          | (seq no)

+-------------------------------+

|           0000000000          | (ack no)

+-------------------------------+

|  8 |   |000010|      8192     | (hdrlen, flags (SYN), win)

+-------------------------------+

|    0xe60a     |         0     | (chksum, urgp)

+-------------------------------+

tcp_input: packed for LISTENing connection.

TCP connection request 22271 -> 21.

tcp_parseopt: MSS

tcp_parseopt: NOP

tcp_parseopt: other

tcp_parseopt: NOP

tcp_parseopt: NOP

tcp_parseopt: other

tcp_enqueue_flags: queuelen: 0

tcp_enqueue_flags: queueing 6510:6511 (0x12)

tcp_enqueue_flags: 1 (after enqueued)

tcp_output: snd_wnd 8192, cwnd 1, wnd 1, effwnd 0, seq 6510, ack 6510

tcp_output: snd_wnd 8192, cwnd 1, wnd 1, effwnd 0, seq 6510, ack 6510, i 0

tcp_output_segment: rtseq 6510

tcp_output_segment: 6510:6510

TCP header:

+-------------------------------+

|    22271      |       21      | (src port, dest port)

+-------------------------------+

|           0032031824          | (seq no)

+-------------------------------+

|           0000006511          | (ack no)

+-------------------------------+

|  5 |   |010000|      8192     | (hdrlen, flags (ACK), win)

+-------------------------------+

|    0x0d59     |         0     | (chksum, urgp)

+-------------------------------+

+-+-+-+-+-+-+-+-+-+-+-+-+-+- tcp_input: flags ACK

-+-+-+-+-+-+-+-+-+-+-+-+-+-+

State: SYN_RCVD

TCP connection established 22271 -> 21.

ftpd_msgaccept: Out of memory

tcp_pcb_purge

tcp_pcb_purge: data left on ->unacked

tcp_abandon: sending RST

tcp_rst: seqno 6511 ackno 32031824.

tcp_slowtmr: no active pcbs/

 

I'm trying to get this working on an ARM board as well, a Sam4e.  Not to get

into too much detail because this is an LWIP mailing list, not an ARM

mailing list, but I imported the FatFs module from the ASF Wizard and used

an example to replicate the FatFs setup.  Seems like one of the #defines

they have me do, "VMEM_NB_SECTOR" determines whether I have enough memory or

not.  The example wants me to set it at 128, whereas the default was 8. At

128 FatFs creates, writes, and reads a file, anything below 128 and FatFs

does not work, however FTP connects but can't do any operations (I get FTP

server error messages).

 

 

 

--

View this message in context: http://lwip.100.n7.nabble.com/TFTP-init-tp28231p28404.html

Sent from the lwip-users mailing list archive at Nabble.com.

 

_______________________________________________

lwip-users mailing list

address@hidden

https://lists.nongnu.org/mailman/listinfo/lwip-users

 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]