nrfConnect Power Profiler not seeing PPK2

Power Profiler app v3.5.0 running in nRF Connect for Desktop v3.12.0 in Ubuntu 220.4 reports "No Supported Devices Connected".

I have used my PPK2 successfully recently, but not today. I upgraded the Power Profiler app to v3.5.0 from v3.4.5 (before trying to connect) and now I can no longer connect to it. PPK2 is pulsing green as expected. `lsusb` shows the Nordic USB device. Tried a different USB cable. Installed nrf-udev_1.0.01-all.deb: made no difference. Ran as root: made no difference.

System report:

# nRFConnect System Report - 2022-09-27T21-07-55.895Z

- System: Dell Inc. OptiPlex 7060
- BIOS: Dell Inc. 1.21.0
- CPU: 1 x Intel Core i7-8700 3.2 GHz 12 cores (6 physical)
- Memory: 19.1 GB free of 23.3 GB total
- Filesystem: /dev/nvme0n1p2 (ext4) 915.3 GB 17.8% used

- OS: Ubuntu (22.04.1 LTS) linux x64

- Versions
- kernel: 5.15.0-48-generic
- git: 2.34.1
- node: 14.16.0
- python: 3.10.6
- python3: 3.10.6
- nrf-device-lib-js: 0.4.13
- nrf-device-lib: 0.12.8
- nrfjprog DLL: 10.16.0
- JLink: JLink_V7.80c

- Connected devices:
- C8E1F5451DE4 : /dev/ttyACM0

Notice the "connected devices" above, which does show the PPK2 on /dev/ttyACM0.

Log (verbose logging did not show anything extra):

17:03:39.763
Using nrf-device-lib-js version: 0.4.13
17:03:39.763
Using nrf-device-lib version: 0.12.8
17:03:39.764
Using nrfjprog DLL version: 10.16.0
17:03:39.764
Using JLink version: JLink_V7.80c
17:03:39.802
Installed JLink version does not match the provided version (V7.66a)

I tried uninstalling the local version of JLink as well: made no difference.

Thanks for any help!

EDIT: Tried the same thing on a fresh install of v3.12.0 on a Windows 10 machine; same problems.

Parents
  • I managed to get things working again. I did an "Add Source", adding https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/3.11-apps/apps.json. Then I ran nRF Connect v3.11.1, installed Power Profiler v3.4.3. It saw the PPK2, but asked to reprogram the firmware. That worked. Then I went back to nRF Connect v3.12.0 and Power Profiler v3.5.0, and it is still seeing the PPK2.

    This is rather mysterious. It seems as if some version of the PPK2 firmware was not compatible. I had upgraded from Power Profiler v3.4.5 to v3.5.0, I think, but can't be sure.

    I was getting crashes with nRF Connect v3.12.0 and Power Profiler v3.5.0, so I reverted to v3.11.0 and v3.4.3. The error in the former was:

    minimumFractionDigits value is out of range.

    RangeError: minimumFractionDigits value is out of range.
        at new NumberFormat (<anonymous>)
        at /home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:26:23556
        at ot (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:26:23598)
        at kr.numeric (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:37231)
        at a (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:19:2681)
        at kr.generateTickLabels (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:45209)
        at kr._convertTicksToLabels (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:48254)
        at kr.update (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:43624)
        at SB (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:68406)
        at Object.update (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:70793)
Reply
  • I managed to get things working again. I did an "Add Source", adding https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/3.11-apps/apps.json. Then I ran nRF Connect v3.11.1, installed Power Profiler v3.4.3. It saw the PPK2, but asked to reprogram the firmware. That worked. Then I went back to nRF Connect v3.12.0 and Power Profiler v3.5.0, and it is still seeing the PPK2.

    This is rather mysterious. It seems as if some version of the PPK2 firmware was not compatible. I had upgraded from Power Profiler v3.4.5 to v3.5.0, I think, but can't be sure.

    I was getting crashes with nRF Connect v3.12.0 and Power Profiler v3.5.0, so I reverted to v3.11.0 and v3.4.3. The error in the former was:

    minimumFractionDigits value is out of range.

    RangeError: minimumFractionDigits value is out of range.
        at new NumberFormat (<anonymous>)
        at /home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:26:23556
        at ot (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:26:23598)
        at kr.numeric (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:37231)
        at a (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:19:2681)
        at kr.generateTickLabels (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:45209)
        at kr._convertTicksToLabels (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:48254)
        at kr.update (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:43624)
        at SB (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:68406)
        at Object.update (/home/halbert/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk/dist/bundle.js:32:70793)
Children
Related