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

[Ø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:

[jseidel]

Alright I have checked the 'Auto device' box, but still have several ports to choose. 

Where can I find the LTE Link Monitor output you need?

What else can I do?


Thanks and regards.

[Øyvind]

I'm sorry if I was unclear, your settings should look exactly like the image I provided. 

Also, I see from the image you provided that you are running AT host sample, is this correct?

You'll find the output log file here:

[jseidel]

Then this should be the output log file:

Fullscreen 2020-06-06T10_09_14.384Z-log.txt Download

2020-06-06T10:09:15.205Z INFO Application data folder: /Users/Jan/Library/Application Support/nrfconnect/pc-nrfconnect-linkmonitor
2020-06-06T10:09:15.430Z DEBUG App pc-nrfconnect-linkmonitor v1.1.1 official
2020-06-06T10:09:15.430Z DEBUG App path: /Users/Jan/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2020-06-06T10:09:15.430Z DEBUG nRFConnect 3.3.3 is supported by the app (^3.2.0)
2020-06-06T10:09:15.430Z DEBUG nRFConnect path: /Applications/nRF Connect.app/Contents/Resources/app.asar
2020-06-06T10:09:15.430Z DEBUG HomeDir: /Users/Jan
2020-06-06T10:09:15.430Z DEBUG TmpDir: /var/folders/jd/xv46yr8d70918sps7n5j8f380000gn/T/
2020-06-06T10:09:15.434Z VERBOSE Could not fetch serial number for serial port at /dev/tty.Bluetooth-Incoming-Port
2020-06-06T10:10:26.758Z INFO Modem port is opened
2020-06-06T10:10:26.763Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-06-06T10:10:35.580Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 110 seconds\x0D\x0A
2020-06-06T10:10:45.569Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 120 seconds\x0D
2020-06-06T10:10:55.558Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 130 seconds\x0D\x0A
2020-06-06T10:11:05.546Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 140 seconds\x0D\x0A
2020-06-06T10:11:15.535Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 150 seconds\x0D\x0A
2020-06-06T10:11:25.524Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 160 seconds\x0D\x0A
2020-06-06T10:11:35.513Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 170 seconds\x0D
2020-06-06T10:11:45.502Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 180 seconds\x0D\x0A
2020-06-06T10:11:55.491Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 190 seconds\x0D\x0A
2020-06-06T10:12:05.479Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 200 seconds\x0D\x0A
2020-06-06T10:12:15.469Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 210 seconds\x0D\x0A
2020-06-06T10:12:25.457Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 220 seconds\x0D
2020-06-06T10:12:35.445Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 230 seconds\x0D\x0A
2020-06-06T10:12:45.434Z DEBUG modem << NRF52840 board control statically configured. DK Uptime is 240 seconds\x0D\x0A

But isn't it the same as I provided you before ?

And yes I've flashed the .hex file for the at commands.

[Øyvind]

I'm sorry, this is still the output from the nRF52840. You will need to check "Auto device/port filter", as mentioned here, and then "Select device".

 

This will automatically select the correct COM port for you to give the correct output.