nrf9160dk_nrf9160 FOTA connection failure

RE: nrf9160dk_nrf9160 FOTA connection failure

AHaug — Tue, 02 Aug 2022 10:23:42 GMT

Hi,

We do not have such an sample, but the Memfault sample application shows you how to use the library: "The Memfault sample shows how to use the Memfault SDK in an nRF Connect SDK application to collect coredumps and metrics. The sample connects to an LTE network and sends the collected data to Memfault’s cloud using HTTPS."

Kind regards
Andreas

RE: nrf9160dk_nrf9160 FOTA connection failure

iivanov — Mon, 01 Aug 2022 13:00:24 GMT

Thank you for response.

Error 111 i assume is #define ECONNREFUSED 111 /* Connection refused */

AT commandw been suggested to run are producing similar results.

If nordic has demo project for nrf9160dk_nrf9160_ns board with FOTA using memfault account could you provide prj.conf so i could reproduce it with my test project and memfault account.

Kind Regards,.

RE: nrf9160dk_nrf9160 FOTA connection failure

AHaug — Thu, 28 Jul 2022 13:22:12 GMT

Hi,

Correct me if you believe I am wrong, but the command "west build -b nrf9160dk_nrf9160_ns -d build/mflt_exmpl C:\ncs\v2.0.0\modules\lib\memfault-firmware-sdk\examples\nrf-connect-sdk\nrf9160\memfault_demo_app --pristine" compiles and builds the entire memfault library, does it not? I believe you only want to flash and build the memfault sample.

[quote user="iivanov"]4.ncs\v1.7.1 attempt been using minimal sample project located in C:\ncs\v1.7.1\nrf\samples\nrf9160\memfault[/quote]

How did this go? Did you have the same results here aswell?

[quote user=""][2022-07-27 14:17:22.706] <err> <mflt>: FOTA start failed, rv=-111[/quote]

Error 111 suggests you have a connection error, which could be caused by either your certificate and/or your internet connection. If this is what causes the issues, could you try to verify if a sample you build from our samples gets connected to the LTE network?

Then, the second thing I would like you to verify/do is to run the AT Client on your custom board and then run the following sequence:

AT+CGMR 
AT%MDMEV=1 
AT%XMODEMSLEEP=1,1000,60000 
AT+CEREG=5 
AT%CESQ=1  
AT%XSYSTEMMODE? 
AT+CFUN=1

This should give you a log similar to the following:

[2022-07-08 17:43:01] *** Booting Zephyr OS build v3.0.99-ncs1  *** 
[2022-07-08 17:43:01] The AT host sample started 
[2022-07-08 17:43:04] AT+CGMR 
[2022-07-08 17:43:05] mfw_nrf9160_1.3.2 
[2022-07-08 17:43:05] OK 
[2022-07-08 17:43:10] AT%MDMEV=1 
[2022-07-08 17:43:10] OK 
[2022-07-08 17:43:14] AT%XMODEMSLEEP=1,1000,60000 
[2022-07-08 17:43:14] O%XMODEMSLEEP: 4 
[2022-07-08 17:43:14] K 
[2022-07-08 17:43:18] AT+CEREG=5 
[2022-07-08 17:43:19] OK 
[2022-07-08 17:43:22] AT%CESQ=1  
[2022-07-08 17:43:23] OK 
[2022-07-08 17:43:27] AT%XSYSTEMMODE? 
[2022-07-08 17:43:28] %XSYSTEMMODE: 1,0,0,0 
[2022-07-08 17:43:28] OK 
[2022-07-08 17:43:31] AT+CFUN=1 
[2022-07-08 17:43:32] %XMODEMSLEEP: 4,0 
[2022-07-08 17:43:32] OK 
[2022-07-08 17:43:33] %CESQ: 46,2,18,2 
[2022-07-08 17:43:33] +CEREG: 2,"7AA9","01444000",7 
[2022-07-08 17:43:34] %MDMEV: SEARCH STATUS 2 
[2022-07-08 17:43:34] +CEREG: 1,"7AA9","01444000",7,,,"00001010","11000001" 
[2022-07-08 17:43:42] %CESQ: 47,2,23,3 
[2022-07-08 17:43:57] %CESQ: 46,2,18,2 
[2022-07-08 17:44:08] %CESQ: 255,0,255,0 
[2022-07-08 17:44:08] %XMODEMSLEEP: 1,1151979975

With the AT Client you may also verify your certificates on the custom board by using %CMNG

Let me know about your progress and results!

Kind regards,
Andreas

RE: nrf9160dk_nrf9160 FOTA connection failure

iivanov — Thu, 28 Jul 2022 01:44:58 GMT

Hi,

1.Firmware upgrade attempts are from 1.7.1 to 1.7.1 and second from 2.0.0 to 2.0.0. Let use v1.7.1.
2.In both cases current firmware software version is 0.1.1 . Active release on memfault account configured from version 0.1.1 to 0.1.3.
3.Upgrade is initiated from firmware uart shell
mflt_nrt fota
4.ncs\v1.7.1 attempt been using minimal sample project located in C:\ncs\v1.7.1\nrf\samples\nrf9160\memfault

Kind Regards

RE: nrf9160dk_nrf9160 FOTA connection failure

AHaug — Wed, 27 Jul 2022 13:54:01 GMT

Hi,

[quote user=""]It is been tried with ncs\v1.7.1 and ncc\v2.0.0. Both did fail.[/quote]

To be able to give you an answer I need to know some more about how/what you are doing that causes this error:

Firstly, how are you performing the update? Are you attempting to upgrade from:

v1.7.1 to v2.0.0 or the other way around?

There has been some changes to MCUBOOT in v2.0.0. As an example in V1.9.1 (and also v.1.7.1)

The default size of MCUBOOT is 48KB on both v1.9.1 and v.2.0.0
The change from v1.9.1 to v2.0.0 is the replacement of SPM (64KB) to TF-M minimal (48KB). This makes start offset of application different
- On V1.9.1 the application start address is 0x20200
- On V2.0.0 the application start address is 0x1c200

You can try to enable CONFIG_TFM_CMAKE_BUILD_TYPE_DEBUG=y to make TF-M size 64KB. This should make the start addresses the same and should allow you to do OTA DFU in between NCS versions. Note that there might be other version changes that might cause issues when trying to migrate versions aswell.

Updates from v1.7.1 to v1.7.1 / v2.0.0 to v2.0.0?

If this is your case, then I will have to ask around some more

Secondly, are these errors present if you attempt with a minimal sample as well? I.e with this sample and DFU update?

Let me know if any of the above helps,

Kind regards,
Andreas