Power Profiler v3.5.5 - Unable to connect to PPK2

[lsoria]

Hi all,

I've just bought an PPK2 and started following the steps of the "Get your Power Profiler Kit II up and running" video in order to test it. Unfortunately, I'm not able to connect to the device (which is recognized) on my desktop computer. This is the log output:

13:42:37.986	Using nrf-device-lib-js version: 0.6.12
13:42:37.986	Using nrf-device-lib version: 0.15.3
13:42:37.986	Using nrfjprog DLL version: 10.19.1
13:42:37.986	Using JLink version: JLink_V7.80c
13:42:42.839	Getting serialport options from persistent store C3CD8708CC4C.pc-nrfconnect-ppk
13:42:42.849	Getting serialport options from persistent store C3CD8708CC4C.pc-nrfconnect-ppk
13:42:50.988	Validating firmware for device with s/n C3CD8708CC4C
13:42:50.991	Opening device with s/n C3CD8708CC4C

The log gets stuck in there, while the PPK2 is "breathing" in green color. Here is a capture of the program:

I tried the same on my laptop, and the PPK2 is both detected and able to connect:

I tried several things like changing the USB port, the cable and even tried disassembling the device to short GND-TP34 and enter in DFU mode, with no luck. Is there anything else I can try on my side in order to help debugging this?

Fullscreen nrfconnect-system-report-2023-07-11T16-47-54.499Z.txt Download

# nRFConnect System Report - 2023-07-11T16-47-54.499Z

- System:     ASUS System Product Name
- BIOS:       American Megatrends Inc. ALASKA - 1072009
- CPU:        1 x AMD Ryzen 9 5900X 12-Core Processor 3.7 GHz 24 cores (12 physical)
- Memory:     54.6 GB free of 63.9 GB total
- Filesystem: C: (NTFS) 1.8 TB 44.8% used

- OS:         Microsoft Windows 10 Pro (10.0.19045) Windows x64

- Versions
    - kernel: 10.0.19045
    - git: 2.39.1.windows.1
    - node: 16.17.1
    - python: 
    - python3: 
    - nrf-device-lib-js: 0.6.12
    - nrf-device-lib: 0.15.3
    - nrfjprog DLL: 10.19.1
    - JLink: JLink_V7.80c

- Connected devices:
    - C3CD8708CC4C : COM6

- Current device:
    - name:          PPK2
    - serialNumber:  C3CD8708CC4C
    - cores:         Unknown
    - website:       https://www.nordicsemi.com/Software-and-tools/Development-Tools/Power-Profiler-Kit-2

Thank you in advance!

[Menon]

Hello,

I'm not able to connect to the device (which is recognized) on my desktop computer.

Are you saying your device is recognized inside the PC but not inside the power profiler Application (nRF connect Desktop)? How's your device displayed inside the Device Manager of your PC?

In both the screenshots I can see PPK2 under the select device section So I am not sure what you mean by "unable to connect".

I tried several things like changing the USB port, the cable and even tried disassembling the device to short GND-TP34 and enter in DFU mode, with no luck. Is there anything else I can try on my side in order to help debugging this?

Can you open the PPK2 inside the programmer App(in nRF connect for desktop), then your PPK2 will automatically switch to bootloader mode (see the first screenshot). Now you can go to the power profiler and select the device open DFU bootloader then it will prompt you to program the device. Can you  try this and report back?

Kind Regards,

Abhijith

[lsoria]

Hi Abhijith, thanks for your answer and apologies if my message wasn't clear.

My first screenshot belongs to my desktop environment, in which the Power Profiler detects the PPK (as it shows) but the connection looks stalled (ie I cannot control the device, which is pulsing/breathing in green color).

On another hand, the second screenshot belongs to my laptop, in which the device is also detected as a PPK2, but after connecting to it the UI changes and I can take measurements and use the device without any issue.

Menon said:

Can you open the PPK2 inside the programmer App(in nRF connect for desktop), then your PPK2 will automatically switch to bootloader mode (see the first screenshot). Now you can go to the power profiler and select the device open DFU bootloader then it will prompt you to program the device. Can you  try this and report back?

Sure! After doing this the device turned red (pulsing) and the power profiler app prompted me to flash the device. However, after clicking Yes the UI got stuck like this:

I had to close the app and unplug the PPK2. On another hand, if I perform the same steps on my laptop the update procedure runs well.

It's obvious that the issue is on my desktop environment, but I cannot figure out what could it be, given that it's a newer machine than my laptop. Feel free to suggest any other thing I could test on my side.

Kind Regards,

Leandro

[Menon]

Hello,

I am not sure why it's stuck in some stage but can you once close the whole nRF connect desktop Application and check whether PPK2 is still visible inside the Programmer and Power Profiler App? Check whether the PPK2 is still in bootloader mode?

It should pulse green if the device is programmed properly from the power profiler App.

 

Kind Regards,

Abhijith

[lsoria]

Hi,

While taking a look at the verbose logs generated on my dektop/laptop environments and searching a little bit, I found this thread in which the reporter suggest closing NZXT CAM app, because it takes control of the COM port associated to their device:

Just want to update this ticket, since it could be helpful for others. The issue, which in the first place seemed to be related to my AMD Ryzen build, was actually related to the NZXT CAM software controlling the water cooling system in the PC build. Whenever I insert the nRF52840 Dongle and it gets enumerated to a COM port, the NZXT CAM software immediately takes control over this port, prohibiting all other software including the nRF Connect for Desktop apps to open this port. By closing the NZXT CAM software everything is working as expected.

Nothing left to say: I have the same app controlling my AIO cooler, so closing it made the PPK2 ready to be used using the Power Profiler app on my desktop. Kudos for navman!

Thank you Abhijith for taking a look at this!

Kind Regards,

Leandro

[Panometric]

NZXT CAM is still a problem. THANKS!