Thingy 91 lost J link only UART avail on nRF connect

[melt]

Good day

After flashing a sample to my thingy  91 I seem to have lost the Jlink connection. All im picking up is the UART via nRF connect Programmer. Is there a Bin file I can drop in the folder to correct it?

Thanks

[melt]

Morning I came accross this post

Connected Devices panel (in vs code) does not discover my device while in the programmer the device can be seen with no issues - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

According to the above you canot program the thing91 with VS code directly, is this why I can see the thingy 91 under connected devices?

Unless im mistaken im sure I saw the thingy 91 when I first connected it out of the box. Also found the LED codes

User Interface module — nRF Connect SDK 1.9.99 documentation (nordicsemi.com)

[Elfving]

melt said:

In VS code what is the difference between  thingy91_nrf9160 and hingy91_nrf9160_ns

NS is referring to the non secure zone of the nRF9160, ie. the modem and peripherals that should be included with it. You can read more about this here.

melt said:

im not picking up my Thingy in VScode or Segger.

What is really being picked up in VSC and SES is the external programmer/debugger. And there is no external programmer on the Thingy91. It does however have MCUBoot, which the nRF Programmer supports. If you want to use VSC and SES you can build using those IDEs and then locate the resulting zephyr.elf file, and flash it using the nRF Programmer. You can also flash the Thingy using the external programmer on another nRF9160DK.

melt said:

Where can I get the meaning of the pulsating LED codes?

Great! Glad you found them.

Regards,

Elfving