nRF9160, File upload via HTTP

RE: nRF9160, File upload via HTTP

Øyvind — Wed, 27 Apr 2022 12:45:33 GMT

Done some testing here using nRF Connect SDK v1.9.1 and connecting to the server in the log output you have provided

2022-04-27T12:28:25.767Z DEBUG modem >> AT#XHTTPCCON=1,"petpace.s3.amazonaws.com",443
2022-04-27T12:28:26.301Z DEBUG modem << #XHTTPCCON: 1
2022-04-27T12:28:26.303Z DEBUG modem << OK
2022-04-27T12:28:27.576Z DEBUG modem << %CESQ: 65,3,17,2
2022-04-27T12:28:29.496Z DEBUG modem << %CESQ: 65,3,23,3
2022-04-27T12:28:38.718Z DEBUG modem >> AT#XHTTPCREQ="GET","/collar-fw.bin","Range: bytes=0-100\r\n"
2022-04-27T12:28:38.728Z DEBUG modem << OK
2022-04-27T12:28:38.737Z DEBUG modem << #XHTTPCREQ: 0
2022-04-27T12:28:38.825Z DEBUG modem << %CESQ: 64,3,18,2
2022-04-27T12:28:48.736Z DEBUG modem << #XHTTPCRSP: 0,-104
2022-04-27T12:28:48.744Z DEBUG modem << #XHTTPCCON: 0

Changing the port to 80 and retrying:

2022-04-27T12:34:36.421Z DEBUG modem >> AT#XHTTPCCON=1,"petpace.s3.amazonaws.com",80
2022-04-27T12:34:37.020Z DEBUG modem << #XHTTPCCON: 1
2022-04-27T12:34:37.024Z DEBUG modem << OK
2022-04-27T12:34:37.978Z DEBUG modem << %CESQ: 64,3,23,3
2022-04-27T12:34:49.691Z DEBUG modem >> AT#XHTTPCREQ="GET","/collar-fw.bin","Range: bytes=0-100\r\n"
2022-04-27T12:34:49.701Z DEBUG modem << OK
2022-04-27T12:34:49.711Z DEBUG modem << #XHTTPCREQ: 0
2022-04-27T12:34:54.143Z DEBUG modem << #XHTTPCRSP:419,1
2022-04-27T12:34:54.148Z DEBUG modem << HTTP/1.1 206 Partial Content
2022-04-27T12:34:54.154Z DEBUG modem << x-amz-id-2: 1GnhGqeMWHk2C/dC8PdTmnID4EEdnx7R/PijytOv5x1YkOta4RDrGswvCGyHuqIkxo0KbffBoUI=
2022-04-27T12:34:54.157Z DEBUG modem << x-amz-request-id: 82WZQAAXF0P8ERJ3
2022-04-27T12:34:54.160Z DEBUG modem << Date: Wed, 27 Apr 2022 12:34:54 GMT
2022-04-27T12:34:54.166Z DEBUG modem << Last-Modified: Sun, 03 Apr 2022 17:09:24 GMT
2022-04-27T12:34:54.168Z DEBUG modem << ETag: "071225a831fc361678aead84b0e34393"
2022-04-27T12:34:54.170Z DEBUG modem << Accept-Ranges: bytes
2022-04-27T12:34:54.172Z DEBUG modem << Content-Range: bytes 0-100/864544
2022-04-27T12:34:54.176Z DEBUG modem << Content-Type: application/octet-stream
2022-04-27T12:34:54.178Z DEBUG modem << Server: AmazonS3
2022-04-27T12:34:54.183Z DEBUG modem << Content-Length: 101
2022-04-27T12:34:54.184Z DEBUG modem << #XHTTPCRSP:101,1
2022-04-27T12:34:54.185Z DEBUG modem << 
2022-04-27T12:34:54.186Z DEBUG modem <<  9E
2022-04-27T12:34:54.187Z DEBUG modem << 5E
2022-04-27T12:34:54.188Z DEBUG modem << 5E
2022-04-27T12:34:54.189Z DEBUG modem << 5E
2022-04-27T12:34:54.190Z DEBUG modem << 5E
2022-04-27T12:34:54.191Z DEBUG modem << 5E
2022-04-27T12:34:54.192Z DEBUG modem << 5E
2022-04-27T12:34:54.192Z DEBUG modem << 5E
2022-04-27T12:34:54.193Z DEBUG modem << 5E
2022-04-27T12:34:54.194Z DEBUG modem << 5E
2022-04-27T12:34:54.195Z DEBUG modem << 5E
2022-04-27T12:34:54.196Z DEBUG modem << 5E
2022-04-27T12:34:54.196Z DEBUG modem << 4Ú
2022-04-27T12:34:54.197Z DEBUG modem << è
2022-04-27T12:34:54.226Z DEBUG modem << 5E
2022-04-27T12:34:54.227Z DEBUG modem << 5E
2022-04-27T12:34:54.227Z DEBUG modem << !º
2022-04-27T12:34:54.228Z DEBUG modem << 5E
2022-04-27T12:34:54.228Z DEBUG modem << 5E
2022-04-27T12:34:54.229Z DEBUG modem << ²
2022-04-27T12:34:54.229Z DEBUG modem << yº
2022-04-27T12:34:54.230Z DEBUG modem << -º
2022-04-27T12:34:54.230Z DEBUG modem << Eº
2022-04-27T12:34:54.232Z DEBUG modem << %º
2022-04-27T12:34:54.232Z DEBUG modem << ù
2022-04-27T12:34:54.233Z DEBUG modem << #XHTTPCRSP:0,1

As you are connecting to port 443, there might be an issue with certificates or the S3 bucket configuration. Have you added AWS credentials to your device?

RE: nRF9160, File upload via HTTP

Øyvind — Mon, 25 Apr 2022 13:39:32 GMT

Looking through the log you have provided, I can see that the error is returned by the function do_http_request() in nrf\applications\serial_lte_modem\src\http_c\slm_at_httpc.c

} else if (httpc.state != HTTPC_COMPLETE) {
		/* Socket was closed by remote */
		err = -ECONNRESET;
		sprintf(rsp_buf, "\r\n#XHTTPCRSP: 0,%d\r\n", err);
		rsp_send(rsp_buf, strlen(rsp_buf));

The log is difficult to read, would it be possible to provide the log as a .txt file?

Are you able to download the same file using e.g. nRF9160: Download Client?

RE: nRF9160, File upload via HTTP

Øyvind — Mon, 25 Apr 2022 13:06:51 GMT

Yes, please attach modem traces as well, to see what goes on inside the modem.

RE: nRF9160, File upload via HTTP

Stas Jis — Mon, 25 Apr 2022 11:06:33 GMT

Øyvind,
No, the problem hasn't been resolved.
What kind of tracing are we talking about, I have already attached the logs above with the tracing settings enabled:
CONFIG_SLM_LOG_LEVEL_DBG=y
CONFIG_NRF_CLOUD_LOG_LEVEL_DBG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y

Or are there other options required?

RE: nRF9160, File upload via HTTP

Øyvind — Mon, 25 Apr 2022 10:29:57 GMT

Hi Stas Jis,

my apologies for the late replay. Have you been able to solve this?

First of all, from nrfxlib\nrf_modem\include\nrf_errno.h #define NRF_ECONNRESET 104 /**< Connection reset */

Could you please provide a modem trace from when you are seeing this issue?

Thanks.

Kind regards,
Øyvind

RE: nRF9160, File upload via HTTP

Øyvind — Wed, 13 Apr 2022 11:12:29 GMT

Hello,

The technical support team will be out due to Easter Holiday until Tuesday April 19. We're sorry for the inconvenience.

I will have a look at the issue but due to Easter holiday will not have answers from our developers.

Kind regards;
Øyvind