Updating the nRF9160 DK

[jseidel]

Hello together, 

I am trying to update the nRF9160 device because I can't get a network connection. 
I followed the guidance of a manual of this site (https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update).

When it comes to the point " ensure the modem is in offline state (AT+CFUN=4)" I get a timed out Error. 

I attached a screenshot which shows the error and also that I have added the "nrf91dk_at_client_long_at_commands" which should prevent it, but didn't helped.

Hope you can help me with something I can try to make it work.

Thanks in Advance and best greetings 

jseidel

[jseidel]

Hello Øyvind, 

with I can't get an network connection I mean that only led3 is blinking when I insert a SIM card and not led4. 
I have tested the SIM card and it should definitely have an NB-IOT connection.

I have now programmed the nrf9160dk_at_client_2020-04-29_bc7ade8b.hex.

And made sure that the SW5 is set to nRF91.

I attached you the LTE Link monitor output and the programmer output.

Best regards, 

jseidel

[jseidel]

Øyvind said:

 Did you remove the SIM card and uncheck "Automatic requests" in the LTE Link Monitor? Did you get any errors?! 

I've done that and didn't got any errors.
In the LTE Link Monitor I get two kind of errors, but independent of those changes: 

- Error while probing devices: Error occured when get serial numbers. Errorcode: CouldNotCallFunction (0x9) Lowlevel error: INVALID_OPERATION (fffffffe)

-> after starting the software

and

- Error: timed out after every at command I try.

Øyvind said:

Did you get any errors while programming this?

No I can easily add it in with drag & drop.

In the programming software I get the error 'Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.'

That's why I can update the firmware of the device and so not the certificates in the lte link monitor.

Øyvind said:

You mention nRF9160 device, what device is this exactly?

It is the nRF9160 Development Kit. 

This one: https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF9160-DK

Greetings, 
jseidel

[jseidel]

ok got some good news! 
after I've downloaded the nRF command Line tools software the nrfConnect programmer recognized the JLINK device and the LTE Link Monitor as well. 

I was able to update the firmware, add the ability to write the nrf9160dk_at_client_2020-04-29_bc7ade8b.hex .
And the AT commands are working. 
When I was trying to update the certificates in the LTE Link Monitor, I got the following errors:

Do you have any help there?

[Øyvind]

Very happy to hear that it fixed the issue with recognizing the device

jseidel said:

When I was trying to update the certificates in the LTE Link Monitor, I got the following errors:

 That's strange. Did you remember to do step two in the guide:
Remove the SIM card and ensure the modem is in offline state (AT+CFUN=4) before updating certificates. Uncheck Automatic requests and use AT+CFUN? to read the state.

If that did not help, can you please provide the output from the LTE Link Monitor? Click on the open log file, save it to your computer, and submit here.

Thanks!

Kind regards,
Øyvind

[jseidel]

I've made sure to remove the SIM card and set the state correctly to AT+CFUN=4, that worked. 

The output have I attached.

2020-05-26T06_42_01.259Z-log.txt

Best regards, 

jseidel

[Øyvind]

I'm sorry, I'm not able to replicate these errors here. Can you please explain the steps that you used to get these

From LTE Link Monitor, check Automatic requests again, connect your board and click the reset button on your board, after that can you please issue the following commands:

AT+CFUN?

//make sure that AT+CFUN? prints several lines.

AT%CMNG=1

Then provide the log again. 

In the previous log you sent it looks like you may not have updated with correct .hex file or it failed:

***** Booting Zephyr OS v1.13.99-ncs1-5025-g745326266d9c *****

While mine using the same .hex file prints:

***** Booting Zephyr OS build v2.0.99-ncs1 *****

Kind regards,
Øyvind

[jseidel]

Alright I flashed all the .hex files again and now the certificate update worked. 

The next step would be the reset of the device. When I try to reset it to make the new certificates work I get the error: 

"There was an error: No device found with id nrf-352656100028722."

Which makes sense because I wasn't able to connect my device to the cloud in general. That's why I tried to follow the guidance of this article (https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update).

But now I am a little stuck what to do next to get a network connection of my nRF9160 DK. 

Do you have any advice?

Best regards, 
jseidel

[Øyvind]

jseidel said:

"There was an error: No device found with id nrf-352656100028722."

Remember to program the asset tracker application again, and then register the device in nRF Cloud.

Can you provide the output from LTE Link Monitor when failing?

Thanks! 

Kind regards,
Øyvind

[jseidel]

Yes I've programmed the asset tracker again. But I can't connect it to the cloud.

That was the main reason I was updating the firmware and certificates, because I wasn't able to connect the board to the network (led3 is blinking but 4 still not).

I am using the sim card of a local provider which is working (I have tested it in a different device).

The error didn't occurred in the LTE Link monitor, it was in the nRF Cloud Account. 

Best regards, 

jseidel

[Øyvind]

Ok, there might be an issue with the steps in the guide and how this is handled in nRF Cloud. 

It will still be good to get the output from the LTE Link Monitor, as it also will show if you are able to connect to the network as intended. 

I will forward it to our nRF Cloud team.

Kind regards,
Øyvind

[jseidel]

Alright. Here is the output of the LTE Link Monitor when I run it:

Fullscreen 2020-05-30T19_42_21.851Z-log.txt Download

2020-05-30T19:42:22.553Z INFO Application data folder: /Users/Jan/Library/Application Support/nrfconnect/pc-nrfconnect-linkmonitor
2020-05-30T19:42:22.803Z DEBUG App pc-nrfconnect-linkmonitor v1.1.1 official
2020-05-30T19:42:22.803Z DEBUG App path: /Users/Jan/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2020-05-30T19:42:22.803Z DEBUG nRFConnect 3.3.3 is supported by the app (^3.2.0)
2020-05-30T19:42:22.803Z DEBUG nRFConnect path: /Applications/nRF Connect.app/Contents/Resources/app.asar
2020-05-30T19:42:22.803Z DEBUG HomeDir: /Users/Jan
2020-05-30T19:42:22.803Z DEBUG TmpDir: /var/folders/jd/xv46yr8d70918sps7n5j8f380000gn/T/
2020-05-30T19:42:22.807Z VERBOSE Could not fetch serial number for serial port at /dev/tty.Bluetooth-Incoming-Port
2020-05-30T19:42:26.350Z INFO Modem port is opened
2020-05-30T19:42:28.946Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 700 seconds\x0D
2020-05-30T19:42:38.935Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 710 seconds\x0D\x0A
2020-05-30T19:42:48.924Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 720 seconds\x0D\x0A
2020-05-30T19:42:58.913Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 730 seconds\x0D\x0A
2020-05-30T19:43:08.902Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 740 seconds\x0D
2020-05-30T19:43:18.891Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 750 seconds\x0D\x0A
2020-05-30T19:43:28.880Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 760 seconds\x0D\x0A
2020-05-30T19:43:38.869Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 770 seconds\x0D
2020-05-30T19:43:48.858Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 780 seconds\x0D
2020-05-30T19:43:58.847Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 790 seconds\x0D\x0A

Best regards, 

jseidel

[Øyvind]

Thank you! Unfortunately, this is the board controller output. At least we have confirmed that it works as intended. Please try with another port, or check the "Auto device/port filter"
 

This should give the following view in the "select device" menu: