FTP support for nrf9160

RE: FTP support for nrf9160

Martin Lesund — Mon, 27 Jul 2020 12:45:12 GMT

Hi Praveen,

Sorry for the delay I have been out of office.
It looks like this has been addressed in the this PR:https://github.com/nrfconnect/sdk-nrf/commit/ffc175f41f0e4a731eae5496373d4a931146ffe0

It is merged with the master branch so if you update NCS and rebuild the application you should have the latest updates.

devzone.nordicsemi.com/.../7652.slm_5F00_ftp_5F00_28_5F00_07.hex

This version also includes the support to change UART baudrate: https://github.com/nrfconnect/sdk-nrf/pull/2571

Best regards,
Martin L.

RE: FTP support for nrf9160

praveenpalaparthi — Wed, 08 Jul 2020 10:38:19 GMT

Hi Martin,

I have tested the build shared "slm_ftp_02_07.hex" and found that now if file name is given wrong its not waiting for infinite time and returning error as shown below.

AT#XFTP="get","testtp.txt"

227 Entering Passive Mode (192,168,1,21,229,252).

ERROR

But if I read FTP status using AT command AT#XFTP="status" after getting response and then If I give any FTP command like to read a file from ftp server or given "ls" command or file name is given wrong, then again its going into infinite loop and not getting any response.

AT#XFTP="open","Administrator","Password1","192.168.1.21"

220 Microsoft FTP Service

200 OPTS UTF8 command successful - UTF8 encoding now ON.

331 Password required

230 User logged in.

AT#XFTP="ls"

227 Entering Passive Mode (192,168,1,21,230,20).

150 Opening ASCII mode data connection.

226 Transfer complete.

testftp.txt

AT#XFTP="get","testftp.txt"

227 Entering Passive Mode (192,168,1,21,230,26).

226 Transfer complete.

ata connection.

30,26).

ow ON.

Hello

AT#XFTP="status"

215 Windows_NT

211-Microsoft FTP Service status:

Logged in user: Administrator

TYPE: ASCII; FORM: NONPRINT; STRUcture: FILE; transfer MODE: STREAM

Data connection: none

211 End of status.

AT#XFTP="get","testftp.txt"

227 Entering Passive Mode (192,168,1,21,230,36).

"Got into infinite loop"

Can we minimize the extra messages for example came for connecting to FTP server using

AT#XFTP="open","Administrator","Password1","192.168.1.2

220 Microsoft FTP Service

200 OPTS UTF8 command successful - UTF8 encoding now ON.

331 Password required

230 User logged in.

Similar messages are also coming for other FTP commands- get,Ls, status

With regards,

Praveen P

RE: FTP support for nrf9160

Martin Lesund — Thu, 02 Jul 2020 07:33:50 GMT

Hi Praveen,

There is now a pull request open for the fixes:

https://github.com/nrfconnect/sdk-nrf/pull/2547

"Decouple Data and Control channel in FTP client for LIST and RETR
commands, leave the synchronization to SLM FTP code. This removes
the infinite wait as stated in problem 1.

No need of update for problem 2.

(the size of message is decided by FTP Server)"

NOTE-1: List a Get will now get Control message first, then Data message, then OK

NOTE-2: Data message by Get could be encoded as hexadecimal but there will be no indication of data type

Sample scenario:

Ready
--> AT+CFUN=1
OK
--> AT+CEREG?
+CEREG: 5,1,"76C1","014ACE00",7,,,"11100000","00001111"
OK
--> AT#XFTP="open",,,"speedtest.tele2.net"
220 (vsFTPd 3.0.3)
200 Always in UTF8 mode.
331 Please specify the password.
230 Login successful.
OK
--> AT#XFTP="ls"
227 Entering Passive Mode (90,130,70,73,96,156).
150 Here comes the directory listing.
226 Directory send OK.
1000GB.zip
100GB.zip
100KB.zip
100MB.zip
10GB.zip
10MB.zip
1GB.zip
1KB.zip
1MB.zip
200MB.zip
20MB.zip
2MB.zip
3MB.zip
500MB.zip
50GB.zip
50MB.zip
512KB.zip
5MB.zip
upload

OK
--> AT#XFTP="ls","-l"
227 Entering Passive Mode (90,130,70,73,110,27).
150 Here comes the directory listing.
226 Directory send OK.
-rw-r--r--    1 0        0        1073741824000 Feb 19  2016 1000GB.zip
-rw-r--r--    1 0        0        107374182400 Feb 19  2016 100GB.zip
-rw-r--r--    1 0        0          102400 Feb 19  2016 100KB.zip
-rw-r--r--    1 0        0        104857600 Feb 19  2016 100MB.zip
-rw-r--r--    1 0        0        10737418240 Feb 19  2016 10GB.zip
-rw-r--r--    1 0        0        10485760 Feb 19  2016 10MB.zip
-rw-r--r--    1 0        0        1073741824 Feb 19  2016 1GB.zip
-rw-r--r--    1 0        0            1024 Feb 19  2016 1KB.zip
-rw-r--r--    1 0        0         1048576 Feb 19  2016 1MB.zip
-rw-r--r--    1 0        0        209715200 Feb 19  2016 200MB.zip
-rw-r--r--    1 0        0        20971520 Feb 19  2016 20MB.zip
-rw-r--r--    1 0        0         2097152 Feb 19  2016 2MB.zip
-rw-r--r--    1 0        0         3145728 Feb 19  2016 3MB.zip
-rw-r--r--    1 0        0        524288000 Feb 19  2016 500MB.zip
-rw-r--r--    1 0        0        53687091200 Jul 24  2014 50GB.zip
-rw-r--r--    1 0        0        52428800 Feb 19  2016 50MB.zip
-rw-r--r--    1 0        0          524288 Feb 19  2016 512KB.zip
-rw-r--r--    1 0        0         5242880 Feb 19  2016 5MB.zip
drwxr-xr-x    2 106      109         69632 Jul 02 09:22 upload

OK
--> AT#XFTP="binary"
200 Switching to Binary mode.
OK
--> AT#XFTP="ls","-l 1KB.zip"
227 Entering Passive Mode (90,130,70,73,93,53).
150 Here comes the directory listing.
226 Directory send OK.
-rw-r--r--    1 0        0            1024 Feb 19  2016 1KB.zip

OK
--> AT#XFTP="get","1KB.zip"
227 Entering Passive Mode (90,130,70,73,109,182).
226 Transfer complete.
data connection for 1KB.zip (1024 bytes).
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OK
--> AT#XFTP="ls","-l 2KB.zip"
227 Entering Passive Mode (90,130,70,73,108,231).
150 Here comes the directory listing.
226 Directory send OK.
OK
--> AT#XFTP="get","2KB.zip"
227 Entering Passive Mode (90,130,70,73,108,196).
ERROR

Here is the precompiled .hex with the fixes --> devzone.nordicsemi.com/.../slm_5F00_ftp_5F00_02_5F00_07.hex

Best regards,
martin L.

RE: FTP support for nrf9160

Martin Lesund — Wed, 01 Jul 2020 13:02:07 GMT

Thnx for the feedback.
This is being handled internally and there should come a PR pretty soon to address this in NCS.

RE: FTP support for nrf9160

praveenpalaparthi — Fri, 26 Jun 2020 03:58:58 GMT

Hi Martin,

I have test FTP in the latest SLM build shared in the mail slm_tcp_proxy_24_06.hex file and here is the log.

1. I found that if file name is given wrong or file is not exist, it got stuck without any information.

2. There is lot of messages like shown in below log, is it possible to minimize these messages?

AT#XFTP="open","Administrator","Password1","192.168.1.21"
220 Microsoft FTP Service
200 OPTS UTF8 command successful - UTF8 encoding now ON.
331 Password required
230 User logged in.
OK

AT#XFTP="status"
215 Windows_NT
211-Microsoft FTP Service status:
     Logged in user: Administrator
     TYPE: ASCII; FORM: NONPRINT; STRUcture: FILE; transfer MODE: STREAM
     Data connection: none
211 End of status.
OK

AT#XFTP="get","testFTP.txt" // File Name is given wrong

227 Entering Passive Mode (192,168,1,21,238,80). //Got stuck here

RE: FTP support for nrf9160

Martin Lesund — Wed, 10 Jun 2020 13:59:10 GMT

Just update NCS to master branch and SLM application will have FTP support as default and the new source code.

cd ncs/nrf
git checkout master
git pull
west update

(confirm that the update is successful by checking the default FTP settings in the Kconfig file)

And to enable TCP proxy as well (if you want the SLM to support that) you would need to enable it in prj.conf file.

CONFIG_SLM_TCP_PROXY=y

(need to apply this fix to run in master: github.com/.../files)

Best regards,

Martin L

RE: FTP support for nrf9160

Martin Lesund — Wed, 03 Jun 2020 13:49:04 GMT

Hi Praveen,
Thank you for the attached log.
From the log, it looks like there may be a problem with establishing the data connection in "passive mode".

Most FTP clients uses "Active mode", which means the FTP server acts as a TCP client and the FTP Client acts as a TCP server. (we only support passive mode)

Is it possible for you to test with another FTP SW like "Filezilla" to test the "passive mode" with the same FTP server. (To confirm functionality)

The FTP client lib. used in the SLM sample should give more information on where you get stuck if you also connect the Jlink RTT viewer.

If you rebuild the sample with the following configuration :

CONFIG_FTP_CLIENT_LOG_LEVEL_DBG=y

in prj.conf it will add even more information in the RTT viewer.

Another option is that we take a modem trace, but I think we can manage with the first options here.

Best regards,
Martin L.

RE: FTP support for nrf9160

Praveen katari — Fri, 29 May 2020 12:25:39 GMT

Hi Martin

here are the logs for issue related to hangingdevzone.nordicsemi.com/.../2020_2D00_05_2D00_28T10_5F00_36_5F00_15.860Z_2D00_log.txt

RE: FTP support for nrf9160

Martin Lesund — Fri, 29 May 2020 11:24:47 GMT

Hi Praveen,
1.

Please provide the full log output when you are testing this since I am not able to replicate the issue.

e.g. When I tested:

AT#XFTP="open","dlpuser@dlptest.com","SzMf7rTE4pCrf9dV286GuNe4N","ftp.dlptest.com"
220-#########################################################
220-Please upload your web files to the public_html directory.
220-Note that letters are case sensitive.
220-#########################################################
220 This is a private system - No anonymous login
200 OK, UTF-8 enabled
331 User dlpuser@dlptest.com OK. Password required
230-Your bandwidth usage is restricted
230 OK. Current restricted directory is /
OK

AT#XFTP="status"
215 UNIX Type: L8
211 https://www.pureftpd.org/
OK

AT#XFTP
ERROR

at#xslmver
#XSLMVER: 1.2
OK

AT#XFTP="pwd"
257 "/" is your current location
OK

Let me double check this with the developer, but from first glance I could not find a supported command for this.

RE: FTP support for nrf9160

Praveen katari — Fri, 29 May 2020 08:43:46 GMT

Hi Martin,

I have verified the above .hex file. it is working fine but i have few small observations.

1. If i send status command(AT#XFTP) i have observed devise is going to unresponsive state. I have to disconnect the board and connect again to device to get response to any AT commands

2. If i want read a data from a file in chunks. I dont see any AT commands supporting this.

Thanks,

Praveen K.

RE: FTP support for nrf9160

Martin Lesund — Thu, 28 May 2020 10:23:00 GMT

Here is the precompiled .hex file for Serial LTE Modem sample with FTP client support and TCP proxy enabled:
devzone.nordicsemi.com/.../SLM_5F00_tcpproxy_5F00_ftp_5F00_28_5F00_05.hex
Note that it's using the default settings:

config SLM_FTP_SERVER_PORT
	int "FTP service port on remote host"
	default 21

config SLM_FTP_USER_ANONYMOUS
	string "FTP client login user Anonymous"
	default "anonymous"
	help
	  Define the user name for anonymous login.

config SLM_FTP_PASSWORD_ANONYMOUS
	string "FTP client login password for user Anonymous"
	default "anonymous@example.com"
	help
	  Define the password for anonymous login.

RE: FTP support for nrf9160

Praveen katari — Thu, 21 May 2020 13:23:41 GMT

Hi Martin,

After few minutes i got below response

2020-05-21T11:01:17.804Z DEBUG modem << *** Booting Zephyr OS build v2.1.99-ncs1 ***\x0D
2020-05-21T11:01:19.726Z DEBUG modem << FTP example\x0D\x0A\x0D
2020-05-21T11:07:09.565Z DEBUG modem << recv_buf:\x0D\x0A\x0D\x0D\x0A\x0D

RE: FTP support for nrf9160

Praveen katari — Thu, 21 May 2020 11:22:08 GMT

Hi Martin,

if i run FTP Clint Sample project with master branch zephry base i am getting an debug print message as as Client_fd = -1; Maybe socket is not created. See below log for details.

2020-05-21T10:45:05.410Z DEBUG modem << SPM: NS image at 0xc000\x0D\x0A
2020-05-21T10:45:05.412Z DEBUG modem << SPM: NS MSP at 0x20023c78\x0D\x0A
2020-05-21T10:45:05.412Z DEBUG modem << SPM: NS reset vector at 0xde99\x0D\x0A
2020-05-21T10:45:05.413Z DEBUG modem << SPM: prepare to jump to Non-Secure image.\x0D\x0A
2020-05-21T10:45:07.253Z DEBUG modem << *** Booting Zephyr OS build v2.1.99-ncs1-2956-g9bab3a84b642 ***\x0D\x0A
2020-05-21T10:45:09.175Z DEBUG modem << FTP example\x0D\x0A\x0D
2020-05-21T10:45:09.179Z DEBUG modem << client_fd: -1\x0D\x0D\x0A

Then i moved zephry base to 1.2.0 branch. I found that above error message is not shown i thing socket is created. I am attaching log more more details.

devzone.nordicsemi.com/.../FTPLogs.txt

I have few question:

1. How to access a file from FTP server with this example code.

2. How to provide FTP credentials from this example code.

I cloned the code on PR-2275. I am able to build and run it.

Can you please provide me the AT commands list for FTP Client. So that i can validate that as well.

Thanks,

Praveen K

RE: FTP support for nrf9160

Stian Røed Hafskjold — Wed, 20 May 2020 11:22:52 GMT

Hi, yes I'm using R&S CMW500. Here is config file for DAU, remote setup, LTE-M1 signalling and NB1 signalling. Hope that helps

devzone.nordicsemi.com/.../DAU_2D00_NB1_2D00_M1.dfl

RE: FTP support for nrf9160

praveenpalaparthi — Wed, 20 May 2020 10:16:13 GMT

Hi Stian,

Are you using R&S CMW500 call box?

Can you share your call box profile file.So that we will quickly load your settings in our call box and try TCP client.

With regards,

Praveen Palaparthi

RE: FTP support for nrf9160

Stian Røed Hafskjold — Tue, 19 May 2020 20:47:57 GMT

Hi Praveen,

What is the IP address of the nRF91 and what is the IP address of the DAU unit? Have you confirmed that they are on the same subnet? Did the nRF91 also get an IP from the same subnet?

Did you connect a network cable to the DAU unit, not just the remote control port? You will usually need two network cables connected to the CMW500. One for remote access, and one separate for the DAU unit.

If you open a "Data Application Measurement" you can start the "IP Analysis" here you will see all socket connections between the UE and the local network. It will show you the source and destination port/addr for all active connections.

You can also start a http or ftp server on the CMW500 DAU. Click on the HTTP or FTP tab and start the server. The IP address of these servers is the same as the DAU unit and is shown in the IP Config window:

Try to open up a connection to port 80 which is the HTTP server and see if that works. In the above example the AT command would be:

    AT#XSOCKET=1,1,0
    AT#XCONNECT="192.168.16.149",80

Are you sure that the TCP server on your local network is reachable? Have you tried connecting to it from other computers on the same network?

I'm using the serial_lte_modem here, the same hex-file as you got from Martin, and there is no problem communicating with the local server through the CMW500.

The TCP "server" is a simple python script that listens to a port on the network. Here is the script:

import socket

s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
s.bind(('',3442))
s.listen(5)

while True:
    (clientsocket, address) = s.accept()
    print(clientsocket, address)

Here are the AT commands sent to the serial lte modem, just to set up a simple test:

Ready

AT%XSYSTEMMODE=1,0,0,0
OK

AT+CEREG=5
OK

AT+CFUN=1
OK

+CEREG: 2,"0001","00000100",7,0,0,"11100000","11100000"
+CEREG: 1,"0001","00000100",7,,,"11100000","11100000"

AT#XSOCKET=1,1,0
#XSOCKET: 1, 1, 0, 6
OK

AT#XCONNECT="192.168.16.153",3442
#XCONNECT: 1
OK

And here is the output from the python scrpt, when the nRF91 (192.168.16.157) connects:

$ python3 tcp_server.py

<socket.socket fd=4, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('192.168.16.153', 3442), raddr=('192.168.16.157', 52236)> ('192.168.16.157', 52236)

RE: FTP support for nrf9160

Martin Lesund — Tue, 19 May 2020 07:25:19 GMT

Hi Praveen,
Let's keep the "Serial LTE Modem" sample out of this discussion since it does not support FTP client yet.
(However, there are some PRs awaiting to get merged that brings FTP client support to the Serial LTE modem Sample: https://github.com/NordicPlayground/fw-nrfconnect-nrf/pull/2275 and https://github.com/NordicPlayground/fw-nrfconnect-nrf/pull/2178)

In Stian's response he used the "FTP Client sample" with the CMW500 and was able to get a connection to the local FTP server.
Could you please share the output log and could you confirm that you followed the callbox steps shown in his answer. Please also make sure you are using the correct IP when building the FTP client sample.

Best regards,

Martin L.

RE: FTP support for nrf9160

Praveen katari — Thu, 14 May 2020 06:55:39 GMT

Hi Stian,

I have configured Call box as you mentioned.

but i still not able to connect .

I have even tried with new hex file (13.05.hex) shared on Serial lte modem i could not able to connect for the TCP server.

Please find the logs in attachments.

devzone.nordicsemi.com/.../8726.Logs.txt

Thanks,

Praveen k.

RE: FTP support for nrf9160

Stian Røed Hafskjold — Tue, 05 May 2020 15:41:21 GMT

Hi, it is my understanding that you are using a CMW500 callbox to do the testing? Based on the IP address of your FTP server, 192.168.1.80, I assume that the FTP server is on your local network and you want the nRF91 to be communicating with this server through the CMW500. So first I want to be sure that you have setup the CMW500 Data Application Unit properly in order to communicate with your local network.

First make sure that your local network is connected to the "LAN DAU" network port on the back side of the CMW500.

Go to the Setup dialog
System section
Click on Go to config, to configure DAU
Open the IP Config tab
Click on Config at the bottom
In the address configuration you can select "DHCP from LAN". Now the DAU and the connected LTE devices will get the IP configuration from the local network. Click apply, and OK.
Verify that the DAU IP address matches the local network subnet.

In the signaling task, after the LTE devices has connected, verity that the given IP address matches the local network subnet:

Also make sure that the "connection type" is set to "Data application" in the Config window:

Now you should be able to communicate with the local FTP server through the FTP client example.

For more information about configuring the CMW500, please refer to the R&S CMW500 user manual or the R&S CMW Data Application Unit user manual.

RE: FTP support for nrf9160

Praveen katari — Wed, 29 Apr 2020 13:52:18 GMT

Hi Martin,

I have started using above app.

I have changes the ip address of my server as shown below

below is the error screen.

RE: FTP support for nrf9160

Martin Lesund — Tue, 21 Apr 2020 11:17:34 GMT

Hi Praveen,
Since this is not an official sample in NCS there is no official documentation for it.

However, I will do my best to help you out with any specific questions you have about it.

RE: FTP support for nrf9160

Praveen katari — Tue, 21 Apr 2020 09:21:57 GMT

Can you provide any documentation which explains the FTP client configuration for nrf9160

RE: FTP support for nrf9160

Martin Lesund — Tue, 21 Apr 2020 08:02:16 GMT

Hi Praveen,
You could use this (unofficial) sample https://github.com/Rallare/fw-nrfconnect-nrf/blob/nrf9160_samples/samples/nrf9160/ftp/src/main.c as a reference point to make a FTP client.