This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Cannot use the SWD between the nRF9160-DK to the Thingy:91

I've recently purchased a Thingy:91 and wasn't able to update its firmware via nRF Connect. I'm guessing this is because that there is no MCUboot on the Thingy:91 that I have. Just to note: the device powers up and connects with nRF Cloud, reports telemetry etc.

I then acquired an nRF9160-DK and an SWD Cable (https://core-electronics.com.au/swd-cable-2x5-pin.html) thinking that I should be able to connect to the Thingy:91 via its Debug Out interface.

However, when I open up nRF Connect/Programmer, the device drop-down appears to show only the nRF9160. Here's a pic:

The Thingy:91 is powered up (its blue light is pulsing as normal), the SWD cables appear to be connected correctly (it doesn't appear possible to connect them wrongly given the notches), the nRF9160-DK is powered up and connected to my Mac... Also, I appear to have the latest updates of nRF Connect and its sub-programs.

Any thoughts/guidance is appreciated.

Parents Reply
  • A pure SWD debugger will recognize only on a SoC level, not a product level. If you have set your nRF9160-DK in 1.8V operation (VDD_IO dip-switch near the main power switch), it should be able to program your thingy91 directly over SWD.

    It’s hard to discern if that particular dip switch is set to 1.8v as it is covered with a plastic film. The nRF9160-dk is brand new. Do you know what its factory position is? Should I remove the film covering the dip switch?

    Also to confirm, should I be able to see the Thingy:91 in the nRF Connect drop down when connected via SWD, or not? Thanks. 

Children
Related