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

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

Øyvind — Tue, 12 Mar 2019 09:03:20 GMT

devzone.nordicsemi.com/.../uicr_5F00_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.

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

Kasturi — Mon, 11 Mar 2019 14:50:48 GMT

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

Please advise on how to troubleshoot this.

Thanks.devzone.nordicsemi.com/.../log-march-11.docx

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

Kasturi — Mon, 11 Mar 2019 14:48:07 GMT

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

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

Øyvind — Fri, 08 Mar 2019 07:36:46 GMT

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.

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

Kasturi — Thu, 07 Mar 2019 21:19:51 GMT

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?

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

Øyvind — Thu, 07 Mar 2019 15:06:11 GMT

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.

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

Kasturi — Thu, 07 Mar 2019 14:29:18 GMT

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

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

Øyvind — Thu, 07 Mar 2019 07:51:01 GMT

[quote user="kbardemed"]I downloaded the firmware and tried to update it as per the readme file. Now I get this error.[/quote]

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

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

Kasturi — Wed, 06 Mar 2019 16:17:08 GMT

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

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

Kasturi — Wed, 06 Mar 2019 16:15:37 GMT

Hi, I have fixed this issue.

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

Øyvind — Wed, 06 Mar 2019 15:05:45 GMT

The error message "...out of range for Intel hex file" is connected to the GNU ARM Embedded toolchain. The latest version has a bug which causes this issue. Please download version GNU Arm Embedded Toolchain: 7-2018-q2-update June 27, 2018 instead.

[quote]

Unable to read connectivity firmware version: Unable to get version info for 960018772: Error occured when get device info. Errorcode: CouldNotOpenDLL (0x7)
Lowlevel error: JLINKARM_DLL_NOT_FOUND

[/quote]

Can you elaborate on what caused this issue? What example did you try to build? There is a similar case here.

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

Øyvind — Wed, 06 Mar 2019 14:57:00 GMT

From this output I can see that your modem FW is outdated. Please download latest FW from this link, under nRF9160 Modem Firmware and Modem DFU Tool. This should fix the connectivity issue.

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

Kasturi — Tue, 05 Mar 2019 20:27:37 GMT

Pledevzone.nordicsemi.com/.../File-requested.txtase see attached.

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

Kasturi — Tue, 05 Mar 2019 15:43:36 GMT

Hi, Yes, I have tried all the steps that you suggested above. Please see the attached word document for output from LTE link manager.

I tried to build the nrf connect sdk project in Segger embedded studio but the build failed. Please see the attached screenshot for reference and kindly help with that as well.

devzone.nordicsemi.com/.../AT-output.docx devzone.nordicsemi.com/.../2019_2D00_03_2D00_05T14_5F00_32_5F00_47.341Z_2D00_log.txt

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

Øyvind — Tue, 05 Mar 2019 10:12:00 GMT

Hello again,

Sorry for the quick response, I misread your question.

Just to ensure that the most obvious steps are done:

Have you tried to log out and in again in nrfcloud? Still no device?
Have you tried to either
- Push the reset button on the DK?
- Switch board to off?
- Unplug and insert the USB
I am sure you probably have tried this:
- Try to add the board one more time?

If none if these steps work, can you please try the AT_Client example? As you have registered the SIM, your should get an LTE link and an IP address. Can you please copy the output from the LTE Link Manager and paste into a .txt file to attach here?

Thank you!
Kind regards,

Oeyvind

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

Kasturi — Mon, 04 Mar 2019 16:40:53 GMT

Yes I have!

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

Øyvind — Mon, 04 Mar 2019 10:18:30 GMT

Hello,

From the nRF Cloud image, have you added the board by clicking on the + sign in the top left?

-Oeyvind

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

Kasturi — Fri, 01 Mar 2019 16:11:14 GMT

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.

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

Kasturi — Fri, 01 Mar 2019 14:23:25 GMT

I am trying to run the asset tracker. I literally just unpacked it, activated the sim, connected it to my PC and tried to add it as an LTE device. LED 3 blinks, does not become steady and LED 4 never lighted up.

Kind regards,

Kasturi Barde

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

Øyvind — Fri, 01 Mar 2019 07:58:49 GMT

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