How to verify which device - Thingy:91 or onboard 9160 - is connected to the Segger JLINK probe on the nrf9160 DK?

[OlaS]

I may be stupid, but I cannot find any indication of which device is currently handled by the nrf9160 DK probe in the nRF Connect Programmer or Segger IDE.

As far as I can the same serial and model numbers are displayed no matter if the probe is handling the external Thingy:91 or the onboard  nrf9160 DK.

See the picture, both devices connected, and JTAG cable between Thingy:91 and nrf9160 DK . 

Current the Thingy:91 is connected and displayed. But I only know this because of the memory map, being of the code currently in the Thingy;91
Clicking the info (i) button displays the serial number of the DK nrf9160, not the Thingy:91 

So how can one verify that the correct device is being programmed and debugged?

[Håkon Alseth]

Hi,

 

I may be stupid, but I cannot find any indication of which device is currently handled by the nrf9160 DK probe in the nRF Connect Programmer or Segger IDE.

Not stupid at all. Quite a common scenario here as well.

I usually program my nRFxx-DK with blinky, then connect another board via the "DEBUG_OUT" port.

Issue a "nrfjprog -e"; if your DK stops blinking, you're not targeting the correct board ;)

 

Another option is to read a unique register (ex. DEVICEID in FICR), or cut the solder bridge for current consumption measurement on the DK (remember to add a jumper wire or similar afterwards!).

 

Kind regards,

Håkon

[OlaS]

Tack Håkon!
Could we hope for an software update that by default displays the relevant FICR registers for the connected processor on start?

[Håkon Alseth]

Hi,

 

OlaS said:

Tack Håkon!

No problem, always happy to help out.

 

OlaS said:

Could we hope for an software update that by default displays the relevant FICR registers for the connected processor on start?

 As the specific register is random generated, it could work, but; then you have to know what the DEVICEID is on your original board as well (or just look at it changing). I can ask it to the nRF connect for desktop team to consider adding such printout/info.

 

Kind regards,

Håkon