NRF Connect Programmer fails to recognize 9160DK

  Over the past 2 weeks the programmer fails to recognize my9160DK board. Instead, I see it listed as "J-Link" in the device list with a serial number underneath. The programmer then refuses to program through that device claiming it is unrecognized.

  I can use nrfjprog commands to flash my device via the command line. However, having the programmer working again would be helpful.

  One other point. This same problem happens on all three 9160DK boards I have.

  Programmer version v3.0.4. Below is the verbose log:

12:09:03.180
Using nrf-device-lib-js version: 0.4.13
12:09:03.181
Using nrf-device-lib version: 0.12.8
12:09:03.181
Using nrfjprog DLL version: 10.16.0
12:09:03.181
Using JLink version: JLink_V7.66a
12:09:03.433
[nrfdl][error](12:09:03.433) [jlink] [NRFJPROG][DebugProbe][] Failed reading the device's family.
12:09:03.456
[nrfdl][error](12:09:03.441) [jlink] [NRFJPROG][nRFXX][] This function cannot be executed without a known family.
12:09:03.627
[nrfdl][error](12:09:03.627) [jlink] [NRFJPROG][HighLevel][] Failed while initializing probe
12:09:08.387
Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.
12:09:08.739
[nrfdl][error](12:09:08.738) [jlink] [NRFJPROG][DebugProbe][] Failed reading the device's family.
12:09:08.756
[nrfdl][error](12:09:08.754) [jlink] [NRFJPROG][nRFXX][] This function cannot be executed without a known family.
12:09:08.941
[nrfdl][error](12:09:08.940) [jlink] [NRFJPROG][HighLevel][] Failed while initializing probe
Parents
  • I was able to fix the problem by uninstalling the Nordic Connect Desktop, Segger JLink and Nordic command line tools, then reinstalling only the Nordic Connect Desktop which pulled/installed the desired Segger tools.

    I suspect the problem may be in the ambiguity in the 32 and 64 bit versions of each of the tools. Nordic Connect has a 32 AND 64 bit install but only appears to be a 32 bit app. Segger has separate 32 and 64 bit versions. The Nordic desktop tools also have separate 32 and 64 bit installers. This is something that should be investigated.

    Doug

Reply
  • I was able to fix the problem by uninstalling the Nordic Connect Desktop, Segger JLink and Nordic command line tools, then reinstalling only the Nordic Connect Desktop which pulled/installed the desired Segger tools.

    I suspect the problem may be in the ambiguity in the 32 and 64 bit versions of each of the tools. Nordic Connect has a 32 AND 64 bit install but only appears to be a 32 bit app. Segger has separate 32 and 64 bit versions. The Nordic desktop tools also have separate 32 and 64 bit installers. This is something that should be investigated.

    Doug

Children
No Data
Related