nRF9160 DK Connecting problems with nRF Cloud

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Fri, 22 Nov 2019 15:14:44 GMT

Hi, I was now finally able to send data from the nRF with a Sim Card from a local provider to my TCP Server. This was the goal, I wanted to accomplish with this ticket and I want to close it now. I wasn't able to connect to nRF Cloud, but for my use-case, that is now not important anymore.

To set up the connection with a TCP Server, I opened a new ticket here, which includes a test project to connect to the Google server:

https://devzone.nordicsemi.com/f/nordic-q-a/53940/connection-problems-to-a-tcp-server

I want to thank you Heidi and bjorn-spockeli for your big help and persistence with me. The Devzone Forum has the best admins I have ever seen!

Thanks for your help and your time! You really helped me a lot with my project!

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Tue, 29 Oct 2019 09:33:24 GMT

Hi!

As this question does not directly relate to the original issue, please make a new ticket. This will make it easier for other users to find questions similar to theirs.

Best regards,

Heidi

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Mon, 28 Oct 2019 20:27:54 GMT

Hi, in the last time, i talked a bit with my local Sim Card provider about the problem and he said the Sim Card is provided with 2 APNs: alliot.nbiot.at and m2m.nbiot.t-mobile.at. The alliot.nbiot.at is the default one and goes over an iot-gateway, which needs to be configurated. The second m2m.nbiot.t-mobile.at is an public APN and doesn't go over the iot-gateway. When I opened the AT client in the LTE Monitor, i was able to connect to the second APN with the command AT+CGDCONT=0,"IP","m2m.nbiot.t-mobile.at".

Is there a command, that I can add to the prj.conf file of my asset_tracker project, so that it takes the second APN? When I use the asset_tracker, it always takes the first APN.

Thanks for your answers!

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Tue, 15 Oct 2019 12:55:10 GMT

You are getting this error because the device isn't connected to nRF Cloud. It has to be connected before you can re-add the device.

I see from your log you are only waiting three minutes for a connection. On average, this takes much longer. Please wait at least 60 minutes before closing the modem. If it still hasn't connected, please attach the output log again.

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Tue, 15 Oct 2019 04:31:48 GMT

Hi, do you mean like this:

Now I have to insert the HWID and then it says the device has to be connected to nrf Cloud. I tried this step a couple of times, but every time I get the error message.

Or do I have to re-add the device somewhere else?

Thanks for your help and answers!

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Mon, 14 Oct 2019 10:08:31 GMT

Hi, did you remember to re-add the device to nRF Cloud before connecting?

You don't have to be able to connect to nRF Cloud to send data to an external server. But I recommend it, so you are sure there is nothing wrong with your device or the connection.

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Sun, 13 Oct 2019 07:37:10 GMT

Hi, I updated the certificate successfully:

On the last step, where you must delete the device from the nrf cloud, it said:

But my nrf never got connected to the cloud anyway, so I might ignore this error message.

Then I flashed the nrf with the asset_tracker again and I updated the host IP address to the prj.conf, but there is error -111 again:

devzone.nordicsemi.com/.../2019_2D00_10_2D00_13T07_5F00_19_5F00_15.499Z_2D00_log.txt

Do you have any ideas?

Another question: The goal of my project with the nrf is to send some data from the nrf to a server. Should this be already be possible in this state? So, I could skip the step of getting into the nrf cloud and focus on sending the data to a server.

Thanks for your help and answers!

RE: nRF9160 DK Connecting problems with nRF Cloud

Terje K Wahl — Fri, 11 Oct 2019 13:45:49 GMT

New thread created: https://devzone.nordicsemi.com/f/nordic-q-a/53152/cloud_connect-failed--111

There you can also read that I've re-tested without static IP, and then DNS lookup fails.

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Fri, 11 Oct 2019 13:17:35 GMT

Hi Terje!

Could you please make a new ticket with your issue? This makes the site much more searchable for our users.

Side note: all networks in Norway support DNS lookup, so I don't think that is your issue.

Best regards,

Heidi

RE: nRF9160 DK Connecting problems with nRF Cloud

Terje K Wahl — Fri, 11 Oct 2019 12:53:02 GMT

Hi, this thread has been very useful for me to get past several problems getting the asset tracker example to work. I connect successfully to a NB-IoT network here in Norway now, thanks to (as explained in other posts here) setting modem mode to NB-IoT, using legacy PCO mode and using a static IP address since DNS is not supported.

Finally, the problem I am left with is "cloud_connect failed: -111". I had high hopes that a certificate update would solve this, but after successfully updating my certificates the same problem still persists.

Here is my output from the terminal:

**** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-2647-gd6e67554cfeb *****
[00:00:00.378,173] 
[0m<dbg> nrf9160_gps.init: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577
Asset tracker started
[00:00:00.389,282] 
[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100223414
[00:00:00.398,498] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100223414/shadow
[00:00:00.410,156] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100223414/shadow/get/accepted
[00:00:00.421,661] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100223414/shadow/get/rejected
[00:00:00.434,204] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100223414/shadow/update/delta
[00:00:00.447,082] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100223414/shadow/update
[00:00:00.458,923] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100223414/shadow/get
Connecting to LTE network. This may take several minutes.
[00:00:00.477,172] 
[0m<inf> lte_lc: Using legacy LTE PCO mode...
[00:00:00.483,428] 
[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0
[00:00:04.653,717] 
[0m<dbg> lte_lc.at_handler: recv: +CEREG: 2,"0CEB","0202791C",9,0,0,"11100000","11100000"
[00:00:04.664,123] 
[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2
[00:00:05.574,218] 
[0m<dbg> lte_lc.at_handler: recv: +CEREG: 1,"0CEB","0202791C",9,,,"11100000","11100000
[00:00:05.584,472] 
[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 1
Connected to LTE network
[00:00:05.595,123] 
[0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 52.54.149.10
cloud_connect failed: -111
LTE link disconnect
Shutdown modem
***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-2647-gd6e67554cfeb *****

Kind regards,

Terje

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Fri, 11 Oct 2019 08:07:32 GMT

Hi, if you get -111 there is an issue with the certificates. Try running through this tutorial and trying again.

Yes, the IP address will change constantly, which is why this is just a workaround to see if the DNS lookup was the actual problem.

For developing and testing, you should be on a network that supports this.

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Thu, 10 Oct 2019 17:24:43 GMT

Thanks! Now I flashed the program on the nrf and I got

cloud_connect failed: -111

devzone.nordicsemi.com/.../2019_2D00_10_2D00_10T17_5F00_09_5F00_29.852Z_2D00_log.txt

Everytime, when I search a ip adress with your link (https://whatismyipaddress.com/hostname-ip)
the IP address of the a2n7tk1kp18wix-ats.iot.us-east-1.amazonaws.com changes. Is this normal?

And do you have an idea what the problem could be?

Thanks for your answers!

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Thu, 10 Oct 2019 09:06:22 GMT

Hi, you need " " around the IP address, so

CONFIG_NRF_CLOUD_STATIC_IPV4_ADDR="52.87.36.155"

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Thu, 10 Oct 2019 04:50:15 GMT

OK, adding the 4 lines

CONFIG_LTE_LEGACY_PCO_MODE=y
CONFIG_NRF_CLOUD_STATIC_IPV4=y
CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y
CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=n

to the prj.conf file worked and I could flash the nrf with it for a test.

When I add the line

CONFIG_NRF_CLOUD_STATIC_IPV4_ADDR=52.87.36.155

to the other lines in the prj.conf then I get this error message:

Loading solution asset_tracker.emProject
Executing load commands
cmake -GNinja -DBOARD=nrf9160_pca10090ns -DBOARD_DIR=C:/Maturaprojekt_Master/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=C:/gnuarmemb -BC:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker/build_nrf9160_pca10090ns -HC:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=C:/SES/arm_segger_embedded_studio_v418_win_x86_nordic/html/configure_nordic_project_menuconfig.py
-- Using application from 'C:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker'
Zephyr version: 2.0.99
-- Selected BOARD nrf9160_pca10090ns
-- Found west: C:/Python37/Scripts/west.exe (found suitable version "0.6.2", minimum required is "0.6.0")
-- Cache files will be written to: C:\Users\Benjamin Bergmann\AppData\Local/.cache/zephyr
USING OUT OF TREE BOARD
-- Loading C:/Maturaprojekt_Master/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090ns.dts as base
-- Overlaying C:/Maturaprojekt_Master/ncs/zephyr/dts/common/common.dts
Device tree configuration written to C:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker/build_nrf9160_pca10090ns/zephyr/include/generated/generated_dts_board.conf

C:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker/prj.conf:90: warning: malformed string literal in assignment to NRF_CLOUD_STATIC_IPV4_ADDR (defined at C:/Maturaprojekt_Master/ncs/nrf\subsys\net\lib\nrf_cloud/Kconfig:17). Assignment ignored.
Parsing Kconfig tree in C:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker/Kconfig
C:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker\src/ui/Kconfig:27: WARNING: dt_str_val is deprecated.
C:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker\src/ui/Kconfig:31: WARNING: dt_int_val is deprecated.
Loaded configuration 'C:/Maturaprojekt_Master/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090ns_defconfig'
Merged configuration 'C:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker/prj.conf'

Error: Aborting due to non-whitelisted Kconfig warning
'C:/Maturaprojekt_Master/ncs/nrf/applications/asset_tracker/prj.conf:90: warning: malformed string
literal in assignment to NRF_CLOUD_STATIC_IPV4_ADDR (defined at
C:/Maturaprojekt_Master/ncs/nrf\subsys\net\lib\nrf_cloud/Kconfig:17). Assignment ignored.'. Note: If
this warning doesn't point to an actual problem, you can add it to the whitelist at the top of
C:/Maturaprojekt_Master/ncs/zephyr/scripts/kconfig/kconfig.py.

CMake Error at C:/Maturaprojekt_Master/ncs/zephyr/cmake/kconfig.cmake:223 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:/Maturaprojekt_Master/ncs/zephyr/cmake/app/boilerplate.cmake:560 (include)
CMakeLists.txt:11 (include)


-- Configuring incomplete, errors occurred!
Project load failed
Reported error: solution load command failed (1)

Is it right, that I use the first IP here?:

Or do I have to use some of the other listed IPs?

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Wed, 09 Oct 2019 07:12:41 GMT

To get to the master branch just run

git checkout master
west update

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Wed, 09 Oct 2019 04:17:12 GMT

So do I have to setup the SDK again, but this time with

git checkout master

command instead of

git checkout v1.0.0

? Or does I have to change the

west init -m github.com/.../fw-nrfconnect-nrf

command?

Or how do I get to the master branch?

Thanks for your answers!

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Tue, 08 Oct 2019 11:13:55 GMT

The configurations I gave you are only defined on the master branch of ncs, not the v1.0.0 tag. Make sure you're on the master branch when building.

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Mon, 07 Oct 2019 18:26:00 GMT

Am I doing this right?:

I open the prj.conf file in the editor, add the lines to the bottom of the file and save it.

Then I try to load the asset tracker in the Segger Embedded Studio, there is an error message:

Loading solution asset_tracker.emProject
Executing load commands
cmake -GNinja -DBOARD=nrf9160_pca10090 -DBOARD_DIR=C:/Maturaprojekt/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=C:/gnuarmemb -BC:/Maturaprojekt_Oktober/ncs/nrf/applications/asset_tracker/build_nrf9160_pca10090ns -HC:/Maturaprojekt_Oktober/ncs/nrf/applications/asset_tracker -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=C:/SES/arm_segger_embedded_studio_v418_win_x86_nordic/html/configure_nordic_project_menuconfig.py
-- Using application from 'C:/Maturaprojekt_Oktober/ncs/nrf/applications/asset_tracker'
Zephyr version: 1.14.99
-- Selected BOARD nrf9160_pca10090
-- Found west: C:/Python37/Scripts/west.exe (found suitable version "0.6.0", minimum required is "0.5.6")
-- Cache files will be written to: C:\Users\Benjamin Bergmann\AppData\Local/.cache/zephyr
USING OUT OF TREE BOARD
-- Loading C:/Maturaprojekt/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090.dts as base
-- Overlaying C:/Maturaprojekt_Oktober/ncs/zephyr/dts/common/common.dts

C:/Maturaprojekt_Oktober/ncs/nrf/applications/asset_tracker/prj.conf:61: warning: malformed string literal in assignment to NRF_CLOUD_STATIC_IPV4_ADDR (defined at ..\nrf\subsys\net\lib\nrf_cloud\Kconfig:17). Assignment ignored.
Parsing Kconfig tree in C:/Maturaprojekt_Oktober/ncs/nrf/applications/asset_tracker/Kconfig
Loading C:/Maturaprojekt/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090_defconfig as base
Merging C:/Maturaprojekt_Oktober/ncs/nrf/applications/asset_tracker/prj.conf

C:/Maturaprojekt_Oktober/ncs/nrf/applications/asset_tracker/prj.conf:64: warning: attempt to assign the value 'y' to the undefined symbol LTE_NETWORK_MODE_NBIOT_GPS

C:/Maturaprojekt_Oktober/ncs/nrf/applications/asset_tracker/prj.conf:65: warning: attempt to assign the value 'n' to the undefined symbol LTE_NETWORK_MODE_LTE_M_GPS

warning: BSD_LIBRARY (defined at ..\nrf\lib\bsdlib\Kconfig:8) has direct dependencies TRUSTED_EXECUTION_NONSECURE with value n, but is currently being y-selected by the following symbols:
- MODEM_INFO (defined at ..\nrf\lib\modem_info\Kconfig:7), with value y, direct dependencies "y" (value: y)

Error: Aborting due to non-whitelisted Kconfig warning
'C:/Maturaprojekt_Oktober/ncs/nrf/applications/asset_tracker/prj.conf:61: warning: malformed string
literal in assignment to NRF_CLOUD_STATIC_IPV4_ADDR (defined at
..\nrf\subsys\net\lib\nrf_cloud\Kconfig:17). Assignment ignored.'. Note: If this warning doesn't
point to an actual problem, you can add it to the whitelist at the top of
C:/Maturaprojekt_Oktober/ncs/zephyr/scripts/kconfig/kconfig.py.

CMake Error at C:/Maturaprojekt_Oktober/ncs/zephyr/cmake/kconfig.cmake:200 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:/Maturaprojekt_Oktober/ncs/zephyr/cmake/app/boilerplate.cmake:529 (include)
CMakeLists.txt:11 (include)


-- Configuring incomplete, errors occurred!
Project load failed
Reported error: solution load command failed (1)

If I load the asset_tracker without changing the prj.conf file, it loads and runs without errors. Do I have to change something else too?

Thanks for your answers!

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Fri, 04 Oct 2019 14:30:01 GMT

Hi, I think I've found the answer but you might not like it.

I suspect the DNS resolve is failing because the network you're on does not support it. A solution presented in this ticket is to add the following to prj.conf in the asset tracker example

CONFIG_NRF_CLOUD_STATIC_IPV4_ADDR=<ip_address>

CONFIG_LTE_LEGACY_PCO_MODE=y

CONFIG_NRF_CLOUD_STATIC_IPV4=y

CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y

and make sure this config is set to n (CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=n).

You can find the IP address to nRF Cloud here:

https://whatismyipaddress.com/hostname-ip

with the nRF cloud host: a2n7tk1kp18wix-ats.iot.us-east-1.amazonaws.com

Then you can add one of the IP-addresses in the prj.conf file.

Note that these IPs can change, so you may need to update this if you want to prototype with nRF Cloud.

Let me know if this works!

Best regards,

Heidi

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Thu, 03 Oct 2019 04:16:17 GMT

Same error again:

devzone.nordicsemi.com/.../2019_2D00_10_2D00_03T04_5F00_11_5F00_53.213Z_2D00_log.txt

It gets the error 22 every time when it trys to connect to nRF Cloud.

Thanks for your answers!

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Wed, 02 Oct 2019 12:58:20 GMT

I suspect it is because your SIM card only supports NB-IoT and the current example you're running is for connecting to LTE-M.

This example supports NB-IoT: devzone.nordicsemi.com/.../nrf91dk_5F00_asset_5F00_tracker_5F00_nbiot.hex

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Wed, 02 Oct 2019 11:13:13 GMT

Here you go!

devzone.nordicsemi.com/.../2019_2D00_10_2D00_02T11_5F00_07_5F00_12.003Z_2D00_log.txt

Thanks for your answers!

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Wed, 02 Oct 2019 08:03:43 GMT

It's called a 10-pin SWD programming cable.

The picture you attached doesn't show me the whole log. Please run the asset_tracker example until the code freezes or the modem shuts down on its own, then press this button in LTE Link Monitor and attach the .txt file in your next comment.

RE: nRF9160 DK Connecting problems with nRF Cloud

Bergmann — Tue, 01 Oct 2019 19:30:01 GMT

Again error 21:

Another question: If I want to flash the Thingy91 with an hex file, i have to connect it like it is shown here:,

https://devzone.nordicsemi.com/f/nordic-q-a/51009/how-do-i-get-output-print-functions-from-app-running-on-thingy-91-that-is-connected-via-cable-to-nrf9160-dk/205039#205039

https://devzone.nordicsemi.com/f/nordic-q-a/51840/how-to-install-at_client-to-thingy-91/208784

When I try to open the board in the nRF Programmer with only a USB cable connected, it say:

Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.

What is the product name of the cable I need here to connect the thingy91 with the nRF9160, that is shown in the pictures in the links?

Thanks for your answers!

RE: nRF9160 DK Connecting problems with nRF Cloud

Heidi — Tue, 01 Oct 2019 08:58:32 GMT

Yes, here you go.

devzone.nordicsemi.com/.../nrf91_5F00_asset_5F00_tracker.hex