Getting started with nRF91

[cmag]

I am testing a nRF9160DK board. I am located in Italy, so LTE-M SIMs would not work.

I have received some NB-IOT SIMs from TIM/Olivetti; I found a compiled sample "at_client.hex" on your site and it seems to be working, even if the programmer app said "Device type unknown" after programming.

I assume that LTE green means that NB-IOT goto connected. The connection information looks fine too.

"Telecom Italia" is the former name of TIM.

I installed the whole toolchain following instructions in the Getting Started Assistant (I had to update some references in the requirements.txt files) and compiled the Asset Tracker application but it seems unable to connect.

I verified that:

/* Set network mode to Narrowband-IoT */
static const char network_mode[] = "AT%XSYSTEMMODE=0,1,0,0";

is active in lte_lc.c

I suspect something is not fine in my setup because I am unable to load the other  project for the "nrf_desktop" application choosing either nrf9160_pca10090 or the ns version.

Do you have a compiled hex of the asset_tracker application that is expected to run with NB-IOT so that I can understand if the problem is with the SIM or the toolchain.

I have installed arm_segger_embedded_studio_v420a_win_x64_nordic from the link in getting started; It offers to upgrade to SEGGER Embedded Studio for ARM version 4.22; should I perform the upgrade?

[MJD093]

Hi,

Could you try adding CONFIG_LTE_NETWORK_MODE_NBIOT=y to the prj.conf file?

That should set the asset tracked to utilise NB-IoT.

[cmag]

I had already added:

# Added for NBIOT as suggested by
# devzone.nordicsemi.com/.../203734
CONFIG_LTE_LEGACY_PCO_MODE=y
CONFIG_LTE_NETWORK_MODE_NBIOT=y

Which activated the line:

static const char network_mode[] = "AT%XSYSTEMMODE=0,1,0,0";

[Håkon Alseth]

Hi,

 

If you recompile the asset_tracker with this option set:

https://github.com/NordicPlayground/fw-nrfconnect-nrf/blob/master/drivers/lte_link_control/Kconfig#L143

ie: prj.conf includes CONFIG_LTE_NETWORK_MODE_NBIOT=y

then you should have NB1 enabled instead of M1.

 

nRF Programmer app has a limitation, where it sets the device as unknown until it has read the whole flash. Its a purely graphical thing, and should not have any impact on the programming procedure. This is notified back to the developers.

 

Kind regards,

Håkon

[cmag]

I have already done that: it is in the posts above.

I have ordered a second unit from DigiKey, to verify if the problem is with the unit I have: I must give an answer by the end of next week if we are able to start development on this platform.

I would be wonderful to have a firmware image verified to work with NB-IOT to exclude problems in the build chain; if this is not possible, I will try with the image I have generated.

[cmag]

I have received the second unit; I guess it is old (pcb 400389/0069TORS).

I have tried everything I could think of (see attachment), but by the end it is back to square 1.

The THINGY:91 works, so TIM SIMs are fine

Asset_tracker recompiled by me seems to work up to the LTE connection

I wonder if t

Fullscreen nRF9160 Experience.txt Download

NEW DEVICE
Switched on: LED3 blinking: does not communicate with LTE Link Monitor
On nrfcloud.com I tried to register as:
352656100221921
CA:08:D5:0D:5F:7E

I get:
There was an error adding your device. 
You might be trying to upgrade an older nRF91 development kit. 
Unless you update your device, you will have to click the 
"Have an old devkit without a PIN?" link below.

I click the link and get:
Power on your LTE device and make sure it is connecting (this could take up to 3 minutes).
When your device has a connection to an LTE tower, LED 3 and LED 4 should be blinking.
Click 'Next' below to move on to the pairing procedure.

I switch the unit off and on again and wait five minutes.

Nothing happens

Before following the instructions on:

https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update

I try to program the app compiled by me with the NB-IoT configuration to see if anything changes.

SES asks to update the fimware of the emulator; I answer YES.

The LTE Link monitor gets no answer. I press RESET.

I get:
SPM: NS image at 0xc000
SPM: NS MSP at 0x2002ad60
SPM: NS reset vector at 0x13db5
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS v1.14.99-ncs2 *****
Application started
LTE LC config ...
ASSERTION FAIL [err == 0] @ ../src/main.c:981
LTE link could not be established.
***** Kernel Panic! *****
Current thread ID = 0x20023570
Faulting instruction address = 0x2e354

Still the LTE Link monitor gets no answer. 

At this point I try to program the nrf9160dk_asset_tracker_09-10-2019_c9c833b1.hex file with nRF Programmer

The unit keeps rebooting and does not give me time to enter commands:
SPM: NS image at 0xc000
SPM: NS MSP at 0x2002c800
SPM: NS reset vector at 0x127a9
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-2647-gd6e67554cfeb *****
[00:00:00.353,576] [1;31m<err> nrf9160_gps: Could not confiugure MAGPIO, error: -8[0m
Asset tracker started[00:00:00.364,227] [0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100221921[0m
[00:00:00.373,565] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100221921/shadow[0m
[00:00:00.385,314] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: $aws/things/nrf-352656100221921/shadow/get/accepted[0m
[00:00:00.397,979] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100221921/shadow/get/rejected[0m
[00:00:00.410,614] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100221921/shadow/update/delta[0m
[00:00:00.423,614] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100221921/shadow/update[0m
[00:00:00.435,546] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100221921/shadow/get[0m
Connecting to LTE network. This may take several minutes.
[00:00:00.453,521] [0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0[0m
LTE link could not be established.
***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-2647-gd6e67554cfeb *****

I try to program the merged.hex file of my application via nRF Programmer

I still get the same assertion failed from the code:

		printk("LTE LC config ...\n");
		display_state = LEDS_CONNECTING;
		err = lte_lc_init_and_connect();
		__ASSERT(err == 0, "LTE link could not be established.");

I start to suspect the the Cellular modem is not updated; I try to update with mfw_nrf9160_1.0.1.zip

Now my application is alive:

The status of LTE Link Monitor is fine (all annunciators are green and Netwwork info is filled correctly)
LED3 ON LED4 Blinking

NRF_CLOUD_EVT_USER_ASSOCIATION_REQUEST
Please enter the user association pattern using the buttons and switches

I try the magic sequence; I get:

NRF_CLOUD_EVT_USER_ASSOCIATION_REQUESTAT+CESQ+CESQ: 99,99,255,255,255,32

At this point I try to update the certificates.

For some time the modem appeared unable to connect; maybe a coincidence, after reflashing from SES it is online again.

Only LED 3 blinking this time.

Tried the connect procedure on nrfclout it agains says I have an old device.

The magic button/switch sequences does not work anymore.

I try again the nrf9160dk_asset_tracker_09-10-2019_c9c833b1.hex file:
After startup I issue the commands:
AT+CFUN=4
AT%XSYSTEMMODE=0,1,0,0
AT+CFUN=0

LTE annunciator remains RED.

After some time and some reboots; in the log I see:

OK[00:00:16.974,365] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0x692ae503[0m

LTE is green

Still only LED 3 is blinking.

But after some time:

AT+CESQ+CESQ: 99,99,255,255,255,37
OK
AT+CESQ+CESQ: 99,99,255,255,255,37
OK
cloud_connect failed: -111
LTE link disconnect
Shutdown modem
***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-2647-gd6e67554cfeb *****
Flash regionDomainPermissions

he problem is just with the nrfcloud link.

Any suggestion?

[Håkon Alseth]

Hi,

 

Based on the last log, the application seems to be running with nrf9160dk_asset_tracker_09-10-2019_c9c833b1.hex, and its able to connect to the network (RSRP is a bit low, 37, -140 + 37 = -103 dBm.), but the certificates are not OK, which is indicated by the -111 connection error.

If you have overwritten the certificates that were already present on the DK (you mentioned that you put in the same certificates as on your thingy:91?), you have to follow the guide here to generate a new certificate for you nRF9160-DK, with a pin number that you generate (123456 for instance), then load that file you get back from nrfcloud.com via "Certificate manager" in LTE Link Monitor, as described here:

https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update

 

Kind regards,

Håkon

[cmag]

I have got both my nRF9160-DK board working.

What I have done is:

1. On "My account" page, Reset the device, even if the device does not actually appear in the account
2. Generate new certificates on "My account" page
3. Manually erase all certificates in memory via AT%CMNG=3,16842753,0, AT%CMNG=3,16842753,1, AT%CMNG=3,16842753,2
4. Load the new certificates using the Certificate manager.

After this I had to power cycle and reset the devices (sometimes it seems that cycling power does not reset properly).

One additional note: each time the IDE is restarted, it overwrites the line:

#define CONFIG_AT_CMD_RESPONSE_MAX_LEN 4000

With 256; then the certificates would not load.