• State Verified Answer
  • Replies 6 replies
  • Subscribers 75 subscribers
  • Views 2139 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 296471
Options

Power Profiler Kit II not visable on Power Profiler v3.5.0

Jasetheace

The issue is as stated in the title.

The 'Select Device' column says "Connect a Nordic development kit to your computer" when the Power Profiler is NOT plugged in. This imediately changes to "No supported devices connected" once the Power Profiller kit is plugged in.

I followed the instructions here to put the Power Profiler kit into bootloader mode but the Power Profiler software still said "No supported devices connected". - devzone.nordicsemi.com/.../366832

The Power Profiler kit presents to the PC as a "nRF52 SDFU USB (COM6)" when it's in bootloader mode.

When in the 'normal mode' (geen led's fading in and out) the kit shows up in the windows device manager as two USB endpoints: 
-nRF Connect DFU Trigger
-nRF Connect USB CDC ACM (COM4)

I've tried this same procedure on two computers. I tried to use a previous version of the nRF Connect software but it still installed the latest Power Profiler software...

-----------------------------------------------------------------------------------------

Power Profiler Kit II HW v1.0.1

nRF Connect for Desktop v3.12.0

Power Profiler v3.5.0

Edition Windows 11 Pro
-Version 21H2
-Installed on ‎2022-‎01-‎26
-OS build 22000.1042
-Experience Windows Feature Experience Pack 1000.22000.1042.0

Parents
  • +1

    Hi Jason and Béla,

    Although I have not been able to reproduce your issue, I've come across identical reports of this issue on DevZone and on GitHub (where I see that Béla has commented), and a similar report from a year ago.

    The reported workaround in these cases was downgrading the Power Profiler version. Could you try downgrading to version 3.4.3? It can be done as follows:

    1. Download the v3.4.3 archive directly from this URL: https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/pc-nrfconnect-ppk-3.4.3.tgz

    2. Place it in C:\Users\%USERPROFILE%\.nrfconnect-apps\local on Windows, or ~/.nrfconnect-apps/local on Linux

    3. Open nRF Connect for Desktop. The app should be visible:

    On my system I can have the old and new version installed side by side. However we used to recommend people to uninstall the newer version first, so please try that if you meet issues.

    Hopefully v3.4.3 now lists your PPK2:

    If the above doesn't work, please try unplugging other connected JLink devices (if any). If that doesn't work, we might have to consider changing the PPK firmware.

    When running v3.4.3 I notice that "Select Device" lists all of my connected nRF devices, while in v3.5.1, only the PPK2 is listed. So my current suspicion is that there is some device filtering going on in the newer versions, and it might be so strict that your PPKs are unintentionally filtered out.

    For reference, I have been unable to reproduce your issue with a similar setup:

    • Windows 11 (Enterprise) 21H2
    • Power Profiler Kit II (PPK2) HW v.1.0.1
    • Both Power Profiler 3.5.0 and the recently released 3.5.1.

    My colleague has tested using:

    • Ubuntu 20
    • PPK2 v.1.0.1
    • Power Profiler 3.5.1.

    On our setups the Power Profiler recognises the PPK and shows the following:

    ^ PPK disconnected

    ^ PPK connected

    I hope the workaround fixes your issue for now. As for an actual solution, I'll see if the PPK team can pinpoint the exact cause, and issue a fix.

    Best regards,

    Raoul Pathak

Reply
  • +1

    Hi Jason and Béla,

    Although I have not been able to reproduce your issue, I've come across identical reports of this issue on DevZone and on GitHub (where I see that Béla has commented), and a similar report from a year ago.

    The reported workaround in these cases was downgrading the Power Profiler version. Could you try downgrading to version 3.4.3? It can be done as follows:

    1. Download the v3.4.3 archive directly from this URL: https://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/pc-nrfconnect-ppk-3.4.3.tgz

    2. Place it in C:\Users\%USERPROFILE%\.nrfconnect-apps\local on Windows, or ~/.nrfconnect-apps/local on Linux

    3. Open nRF Connect for Desktop. The app should be visible:

    On my system I can have the old and new version installed side by side. However we used to recommend people to uninstall the newer version first, so please try that if you meet issues.

    Hopefully v3.4.3 now lists your PPK2:

    If the above doesn't work, please try unplugging other connected JLink devices (if any). If that doesn't work, we might have to consider changing the PPK firmware.

    When running v3.4.3 I notice that "Select Device" lists all of my connected nRF devices, while in v3.5.1, only the PPK2 is listed. So my current suspicion is that there is some device filtering going on in the newer versions, and it might be so strict that your PPKs are unintentionally filtered out.

    For reference, I have been unable to reproduce your issue with a similar setup:

    • Windows 11 (Enterprise) 21H2
    • Power Profiler Kit II (PPK2) HW v.1.0.1
    • Both Power Profiler 3.5.0 and the recently released 3.5.1.

    My colleague has tested using:

    • Ubuntu 20
    • PPK2 v.1.0.1
    • Power Profiler 3.5.1.

    On our setups the Power Profiler recognises the PPK and shows the following:

    ^ PPK disconnected

    ^ PPK connected

    I hope the workaround fixes your issue for now. As for an actual solution, I'll see if the PPK team can pinpoint the exact cause, and issue a fix.

    Best regards,

    Raoul Pathak

Children
No Data
Related
Terms of service