Unable to connect to LTE using nrf9160 dk

RE: Unable to connect to LTE using nrf9160 dk

harisahmed — Sat, 14 Mar 2020 17:52:54 GMT

Hi,

Following your instructions I recompiled the source code for nrf9160dk using pca10090ns as the board and set

CONFIG_LTE_NETWORK_MODE_NBIOT_GPS = y

. After this I was able to connect to LTE but couldn't communicate with the cloud.

Then, I tried running cloud connect on my nrf9160dk and found this to be the output:

So, I reset the device from the nrf Cloud and updated the certificates and connected to the cloud using asset tracker application. This time I was successful and can see the data being sent onto the cloud.

In conclusion, the problem was with the certificates.

RE: Unable to connect to LTE using nrf9160 dk

Håkon Alseth — Mon, 09 Mar 2020 08:03:05 GMT

[quote user="harisahmed"]Can you tell me what is the difference between the hex files present in images_full and images_dfu_hex. I am using images_full version for my nrf9160 dk as I can see the LEDs blinking only on the dk only in this version and for thingy91 I am using images_dfu_hex version.[/quote]

Here's the .txt file from the .zip:

These files were built with nRF Connect SDK version v1.1.0
from repository at https://github.com/NordicPlayground/fw-nrfconnect-nrf

Full commit SHA: d3130d77559e2206a2541b09dd26e9be2f8532ed

Package contents:
images_full/      Full firmware images, updated over debug probe / development kit
images_dfu_hex/   Application images, updated over USB, HEX format
images_dfu_bin/   Application images, updated over USB, binary format

File                                                                       Description
-------------------------------------------------------------------------  ------------------------------------------------------------------------
images_dfu_bin/thingy91_at_client_dfu_2019-11-29_d3130d77.bin              Firmware for direct modem communication
images_dfu_bin/thingy91_ltem_dfu_2019-11-29_d3130d77.bin                   Asset tracker firmware for nRF9160, LTE-M network mode
images_dfu_bin/thingy91_nbiot_dfu_2019-11-29_d3130d77.bin                  Asset tracker firmware for nRF9160, NB-IoT network mode
images_dfu_bin/thingy91_nbiot_legacy_pco_dfu_2019-11-29_d3130d77.bin       Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO mode
images_dfu_bin/thingy91_nrf52_usb_uart_bridge_dfu_2019-11-29_d3130d77.bin  USB-UART bridge for nRF52840
images_dfu_hex/thingy91_at_client_dfu_2019-11-29_d3130d77.hex              Firmware for direct modem communication
images_dfu_hex/thingy91_ltem_dfu_2019-11-29_d3130d77.hex                   Asset tracker firmware for nRF9160, LTE-M network mode
images_dfu_hex/thingy91_nbiot_dfu_2019-11-29_d3130d77.hex                  Asset tracker firmware for nRF9160, NB-IoT network mode
images_dfu_hex/thingy91_nbiot_legacy_pco_dfu_2019-11-29_d3130d77.hex       Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO mode
images_dfu_hex/thingy91_nrf52_usb_uart_bridge_dfu_2019-11-29_d3130d77.hex  USB-UART bridge for nRF52840
images_full/thingy91_at_client_2019-11-29_d3130d77.hex                     Firmware for direct modem communication
images_full/thingy91_ltem_2019-11-29_d3130d77.hex                          Asset tracker firmware for nRF9160, LTE-M network mode
images_full/thingy91_nbiot_2019-11-29_d3130d77.hex                         Asset tracker firmware for nRF9160, NB-IoT network mode
images_full/thingy91_nbiot_legacy_pco_2019-11-29_d3130d77.hex              Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO mode
images_full/thingy91_nrf52_usb_uart_bridge_2019-11-29_d3130d77.hex         USB-UART bridge for nRF52840
mfwnrf9160110.zip                                                          Modem firmware, updated through nRF Connect for Desktop

The files tagged with "dfu" needs to be programmed over UART, by interfacing MCUboot, provided both in .bin and .hex format.

Those located in the full/ folder needs to be programmed using an external debugger (for instance the nRF9160-DK)

[quote user="harisahmed"]I am using images_full version for my nrf9160 dk[/quote]

These images are compiled for the thingy:91, and will not run properly on the nRF9160-DK. For the DK, please compile asset_tracker for board "nrf9160_pca10090ns".

Kind regards,

Håkon

RE: Unable to connect to LTE using nrf9160 dk

harisahmed — Fri, 06 Mar 2020 17:31:26 GMT

Actually, thingy91_nbiot_dfu_2019-11-29_d3130d77.hex is also working on my Thingy91 without any problems. So I don't think that new PCO is the problem with my local carrier. Any other suggestions?

Can you tell me what is the difference between the hex files present in images_full and images_dfu_hex. I am using images_full version for my nrf9160 dk as I can see the LEDs blinking only on the dk only in this version and for thingy91 I am using images_dfu_hex version.

RE: Unable to connect to LTE using nrf9160 dk

Håkon Alseth — Fri, 06 Mar 2020 14:06:09 GMT

Hi,

If the asset_tracker only works with this firmware image:

[quote user=""]thingy91_nbiot_legacy_pco_dfu_2019-11-29_d3130d77.hex[/quote]

It means that your local carrier does not support the "new" protocol configuration options (PCO for short), and you have to default to use the legacy PCO when building asset_tracker, by adding this to the prj.conf file:

CONFIG_LTE_LEGACY_PCO_MODE=y

This will ensure that the lte_lc library enables legacy PCO. Could you try this and see if it works when manually compiling asset_tracker?

Kind regards,

Håkon