nRF Connect v3.2.0 issue for nFR9160

[Dheeraj]

Hi, 

I am new to Nordic Thingy91.

I have tried to connect Nordic Thingy91 (nRF9160) device using "nRF connect v3.2.0", via USB.
But I am facing, below issue.

Issue 1: "unsupported device: the detected device could not be recognized as neither jlink device nor nordic USB device for windows 10"

Tried: I have tried installing different versions of J-Link from below:
www.segger.com/.../
(Tried with: 6.22g,e 6.50e, etc.,)

But no luck, and below issue is seen,

Issue 2: "unsupported device with serial number PCA_20035_d081421f4d65 and trails ["serialport"]"

Is JTAG necessary to flash/program the "nRF9160" and "nRF52840"..?

Host Machine Details (Where I am trying to flash/Program the nRF9160):
Windows 10
nRF Connect v3.2.0

NOTE: Apart from nRF Connect v3.2.0, I didn't installed any tools in windows 10 machine.
I have a Nordic Thingy91 development environment (including SEGGER) in a different machine. Planing to use windows 10 to flash/program the nRF9160 remotely.

I was able to successfully compile and generate the binary (Ex: Asset tracking) in the development environment.

Please direct me to the correct path, whether I am missing anything on Windows 10 machine to flash/program the nRF9160.

Thank you for your help.

[Didrik Rokhaug]

Hi.

There are two ways to program the Thingy:91:

1. With an external debugger. E.g. you can connect an SWD cable between the "Debug out" header on an nRF91 DK and the 10-pin connector on the Thingy. Then in the programmer app, you must select the nRF91 DK.

2. Using MCUBoot. For more information see this guide: https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/thingy91_2d00_fw_2d00_update_2d00_mcuboot

Best regards,

Didrik

[Dheeraj]

Hi Didrik, 

Thank you for the quick reply. 

As I mentioned in the above description, I am getting errors (Issue1 & 2) "unsupported device...",  while connecting the nRF9160 using "nRF Connect v3.2.0". Please refer to the screenshot attached. 

The connection was NOT successful between the Host machine and nRF9160 DK to flash/program it, 

Could you please help with this. 

[Didrik Rokhaug]

The programmer application expects to connect to a segger programmer chip, such as the one on the nRF9160 DK. The Thingy does not have such a chip.

You must, therefore, connect the Thingy to the "Debug out" header on the DK, and connect to the DK in the Programmer application, or use the MCUBoot method I mentioned.

[Dheeraj]

Hi Didrik,

Thanks for the info. We are able to flash thingy91 (nrf9160_pca20035ns) successfully using MCUBoot. 

As per the link shared  (MCUBoot procedure)above the Image in /build/zephyr/app_update.bin is suitable for nRF91600 SiP, but what is the appropriate Image for nRF52840 SoC .? 

What is the difference between Nordic Thingy91 (PCA20035) and nRF Connect DK (PCA10090)..?? 

[Didrik Rokhaug]

Dheeraj said:

what is the appropriate Image for nRF52840 SoC .? 

The nRF52840 on the Thingy:91 is programmed with this sample: https://github.com/NordicPlayground/fw-nrfconnect-nrf/tree/master/samples/usb/usb_uart_bridge

As it does not use MCUBoot, you will have to use a debugger to be able to program the nRF52840.

The nRF9160 Development Kit (DK) comes with a programmer, and have all the pins of the nRF9160 SiP exposed. It also has multiple buttons and LEDs. It is the most convenient platform for development on the nRF9160.

The Thingy:91 has several sensors, and therefore it might be better suited for prototyping and demos.