NRF9160-DK - LED 4 fails to blink on the kit.

[Kasturi]

Hi, I am in the initial stages of starting development with nRF9160-DK. At this step, the LED 4 on the board absolutely does not blink. I have tried taking the kit to different places too, for better connectivity but with no luck. 

How can I troubleshoot it?

[Øyvind]

Hello,

What application is running on your kit? What is the status on LED 3? Has your kit been used by someone before you, e.g. has it been registered to another nRF Cloud account?

Kind regards,
Oeyvind

[Kasturi]

So I went back and reactivated the sim card and tried the first step again (LED 3 and 4 both blink).

I go to the next step that was the pairing sequence after which LED 4 blinked for a while and turned solid. But I still can not see the kit added as a device.

According to this article: https://devzone.nordicsemi.com/tutorials/b/getting-started/posts/getting-started-with-nrf9160-dk#h69sjqflk6om1o8mdrn1vfnph47lq1r7

The kit should be added as a device at this point. Please help me with what could be going wrong. 

Thanks.

[Øyvind]

Kasturi said:

I downloaded the firmware and tried to update it as per the readme file. Now I get this error.

 Were you able to update the FW after fixing the issue?

[Kasturi]

No, I have attached a screenshot to show what error I get when I try to update the firmware.

[Øyvind]

Have you done what was suggested in this case I linked to:
https://devzone.nordicsemi.com/f/nordic-q-a/36118/nrf-connect-mac-v-2-4-0-can-t-scan/139428

jlinkARM.dll is a part of J-Link Software and Documentation pack. Please download the latest version, and see if this solves the error.

[Kasturi]

Hi, I successfully updated the firmware on the kit. What are the next steps in resolving the connectivity issue?

How do I check if this has fixed the connectivity issue?

[Øyvind]

Good to hear that you were able to update the FW. 

The next step is to go back to my previous comment, click here. Please follow the instructions I gave there.

[Kasturi]

Hi I tried to follow the steps. The log shows this:

10:41:32.657

Application data folder: C:\Users\kbarde\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor

10:41:37.382

Modem port is opened

10:43:53.345

Error: 'AT+CFUN=1 ' timed out

10:43:58.930

Error: 'AT+CFUN=1 ' timed out

10:45:30.433

Error: 'AT+CGSN=1 ' timed out

10:45:40.729

Error: 'AT+CGSN=1AT+CGMI ' timed out

10:45:46.125

Error: 'AT+CGMI ' timed out

The Terminal output is:

AT+CFUN?

***** Booting Zephyr OS v1.13.99-ncs2 *****

Secure Boot: configure flash

Secure Boot: SPU: set region 0 as Secure

Secure Boot: SPU: set region 1 as Secure

Secure Boot: SPU: set region 2 as Secure

Secure Boot: SPU: set region 3 as Secure

Secure Boot: SPU: set region 4 as Secure

Secure Boot: SPU: set region 5 as Secure

Secure Boot: SPU: set region 6 as Secure

Secure Boot: SPU: set region 7 as Secure

Secure Boot: SPU: set Flash region 8 as Non-Secure

Secure Boot: SPU: set Flash region 9 as Non-Secure

Secure Boot: SPU: set Flash region 10 as Non-Secure

Secure Boot: SPU: set Flash region 11 as Non-Secure

Secure Boot: SPU: set Flash region 12 as Non-Secure

Secure Boot: SPU: set Flash region 13 as Non-Secure

Secure Boot: SPU: set Flash region 14 as Non-Secure

Secure Boot: SPU: set Flash region 15 as Non-Secure

Secure Boot: SPU: set Flash region 16 as Non-Secure

Secure Boot: SPU: set Flash region 17 as Non-Secure

Secure Boot: SPU: set Flash region 18 as Non-Secure

Secure Boot: SPU: set Flash region 19 as Non-Secure

Secure Boot: SPU: set Flash region 20 as Non-Secure

Secure Boot: SPU: set Flash region 21 as Non-Secure

Secure Boot: SPU: set Flash region 22 as Non-Secure

Secure Boot: SPU: set Flash region 23 as Non-Secure

Secure Boot: SPU: set Flash region 24 as Non-Secure

Secure Boot: SPU: set Flash region 25 as Non-Secure

Secure Boot: SPU: set Flash region 26 as Non-Secure

Secure Boot: SPU: set Flash region 27 as Non-Secure

Secure Boot: SPU: set Flash region 28 as Non-Secure

Secure Boot: SPU: set Flash region 29 as Non-Secure

Secure Boot: SPU: set Flash region 30 as Non-Secure

Secure Boot: SPU: set Flash region 31 as Non-Secure

Secure Boot: configure SRAM

Secure Boot: SPU: set SRAM region 0 as Secure

Secure Boot: SPU: set SRAM region 1 as Secure

Secure Boot: SPU: set SRAM region 2 as Secure

Secure Boot: SPU: set SRAM region 3 as Secure

Secure Boot: SPU: set SRAM region 4 as Secure

Secure Boot: SPU: set SRAM region 5 as Secure

Secure Boot: SPU: set SRAM region 6 as Secure

Secure Boot: SPU: set SRAM region 7 as Secure

Secure Boot: SPU: set SRAM region 8 as Non-Secure

Secure Boot: SPU: set SRAM region 9 as Non-Secure

Secure Boot: SPU: set SRAM region 11 as Non-Secure

Secure Boot: SPU: set SRAM region 12 as Non-Secure

Secure Boot: SPU: set SRAM region 13 as Non-Secure

Secure Boot: SPU: set SRAM region 14 as Non-Secure

Secure Boot: SPU: set SRAM region 15 as Non-Secure

Secure Boot: SPU: set SRAM region 16 as Non-Secure

Secure Boot: SPU: set SRAM region 17 as Non-Secure

Secure Boot: SPU: set SRAM region 18 as Non-Secure

Secure Boot: SPU: set SRAM region 19 as Non-Secure

Secure Boot: SPU: set SRAM region 20 as Non-Secure

Secure Boot: SPU: set SRAM region 21 as Non-Secure

Secure Boot: SPU: set SRAM region 22 as Non-Secure

Secure Boot: SPU: set SRAM region 23 as Non-Secure

Secure Boot: SPU: set SRAM region 24 as Non-Secure

Secure Boot: SPU: set SRAM region 25 as Non-Secure

Secure Boot: SPU: set SRAM region 26 as Non-Secure

Secure Boot: SPU: set SRAM region 27 as Non-Secure

Secure Boot: SPU: set SRAM region 28 as Non-Secure

Secure Boot: SPU: set SRAM region 29 as Non-Secure

Secure Boot: SPU: set SRAM region 30 as Non-Secure

Secure Boot: SPU: set SRAM region 31 as Non-Secure

Secure Boot: configure peripherals

Secure Boot: MSP_NS 200265f0

Secure Boot: prepare to jump to Non-Secure image

***** Booting Zephyr OS v1.13.99-ncs2 *****

The AT host sample started

AT+CFUN?

+CFUN: 4

OK

AT+CFUN=1

OK

AT+CFUN=1

AT+CFUN=1

AT+CGSN=1

AT+CGSN=1AT+CGMI

AT+CGMI

[Kasturi]

The log file is attached here. Please observe that log says "Error: At command timed out"

Please advise on how to troubleshoot this. 

Thanks.log march 11.docx

[Øyvind]

uicr_tcxo.hexMy apologies for this being so difficult. We are aware that there are some issues, and we working with a solution.

Can you please try to reset the board and see what this does? After this try power cycling the board once. 
Then, if that does not fix the solution, please program the attached file using:

nrfjprog --program uicr_tcxo.hex --sectorerase -f nrf91 -r --verify

This file will fix the config of 32 MHz temperature compensated crystal oscillator (TCXO) in UICR.

After this, try to run the at_client example one more time.