Stephen Cowell wrote
> Some confusion... your board, your design, is an FTP server? You are
> pushing files from a PC client to an embedded server.
> I'm assuming no OS... raw, in other words.
FTP, TFTP, HTTP, doesn't matter to me. I just want to transfer a file from
my PC, an image file, to my
Nick... I'm using the same ftp... and the same processor... I wrote sftp
but it's actually ftpd, from toelke.
Some confusion... your board, your design, is an FTP server? You are
pushing files from a PC client to an embedded server.
I'm assuming no OS... raw, in other words.
Do you have the
Tim Cussins wrote:
We've encountered a couple of interesting http servers in the wild that
redirect, then send a TCP RST immediately.
[..]
In our case, the data for the redirect appears to make it into LWIP, but
the subsequent RST causes the pcb to be discarded before we have an
opportunity to re
Hi all,
We've encountered a couple of interesting http servers in the wild that
redirect, then send a TCP RST immediately.
Some http servers do this to avoid the TIME_WAIT state. Viz:
https://support.microsoft.com/en-gb/kb/272933
In our case, the data for the redirect appears to make it into
Jan Menzel wrote
> Hi Ajay!
> If sending an image is all you wont to do, you might consider using
> tftp. tftp is especially designed for this purpose, requires only udp
> but lacks features like authentication. Many bootloaders use tftp to
> boot using an image located on the network.
>
>
Stephen Cowell wrote
> What ftp library are you using? I successfully used sftp with lwip
> 1.4.1 and fatFS, no OS needed, to be an FTP server for an SD card.
>
> Are you being a server or a client? Sounds like client. Pretty sure
> all the ftp things need a file system to work.
>
> Using a
It's not me but Nicholas is looking for an ftp server. I am not quite sure
what's his exact requirements.
-- Ajay
On Jan 18, 2017 10:31 PM, "Jan Menzel" wrote:
Hi Ajay!
If sending an image is all you wont to do, you might consider using
tftp. tftp is especially designed for this purpos
Hi Ajay!
If sending an image is all you wont to do, you might consider using
tftp. tftp is especially designed for this purpose, requires only udp
but lacks features like authentication. Many bootloaders use tftp to
boot using an image located on the network.
Jan
On 18.01.2017 14:
What ftp library are you using? I successfully used sftp with lwip
1.4.1 and fatFS, no OS needed, to be an FTP server for an SD card.
Are you being a server or a client? Sounds like client. Pretty sure
all the ftp things need a file system to work.
Using a file system is going to be easier
Ajay Bhargav wrote
> 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
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 op
Hello
I work on a project which use FreeRTOS and Lwip v 1.4.1. I'm using a
LandTiger board which is made on an NXP LPC1768. My project is based on
LPCOpen 2.10 and derivated from the “lwip_tcpecho_freertos” example. I'm
only using the Socket API.
In TCP, everything is OK! but in UDP doesn't...
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
13 matches
Mail list logo
