PPK2 "No device setup found"

[Tangent_tracker]

Hi folks, so I will start by saying I have had this device working at home under Windows 11. I have brought the device to work to use on my works computer, which is still windows 10 (work for a uni, they don't seem to be in a hurry switching lol).

I have full admin rights on my machine... 

So I have installed PP V431 through NRF connect.

Plugged my PPK2 and loaded POwer Profiler.. The device of mine is listed, but when I click on the item it fails to load with the following error

13:39:42.664	Initialising the bundled nrfutil device
13:39:43.106	Using the bundled core version for nrfutil device: 8.0.0
13:39:43.144	Using nrfutil-device version: 2.10.2
13:39:43.144	Using nrf-device-lib version: 0.17.71
13:39:43.144	Using nrf-probe version: 0.38.0
13:39:43.144	Using JLink version: JLink_V9.24a
13:39:43.146	Your version of SEGGER J-Link (9.24a) is newer than the one this app was tested with (8.18). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.
13:39:43.220	Getting serial port options from the persistent store for CE9C1EEC7811.pc-nrfconnect-ppk
13:39:43.222	Device connected with the serial number CE9C1EEC7811
13:40:07.870	Selecting device with the serial number CE9C1EEC7811
13:40:08.157	Selected device with the serial number CE9C1EEC7811
13:40:08.158	Note: no pre-compiled firmware is available for the selected device.
13:40:08.158	Error while setting up device with the serial number CE9C1EEC7811
13:40:08.159	"No device setup found"
13:40:08.159	Deselected device

 
I have also tried plugging into a powered USB3 hub, and I get the same error, so don't think it is due to unstable power as has been suggested on a similar thread...

Is there anything I can try to increase the odds of getting this to work on this machine?

Thanks

[Tangent_tracker]

Just a bit more info - when i go to quickstart, my device is greyed out with the words "Not supported yet". The only time I previously saw this was when I had not installed Power Profile on the last machine. 

[Einar Thorsrud]

Hi,

Windows 10 is no longer tested (currently tier 3 level support), but it should work. From the log it looks like there is problems with the USB serial driver (Usbser.sys), which should be installed automatically. I am not able to say why this happened, though.

[Tangent_tracker]

Thanks Einar, yes it comes up with PK2 at work under coms but different at home... Tried deleting drivers, still the same issue... It's a little frustrating to say the least as I wanted to demonstrate to my boss. 

Hopefully the uni will make a decision at some point, we all need new PC's as well, which is the main stalling point I think!

[Reiner]

Same issue under a heavily used older Windows 10 installation:

15:50:06.292 Selected device with the serial number C9285F8D9C3615:50:06.293 Note: no pre-compiled firmware is available for the selected device. 15:50:06.293 Error while setting up device with the serial number C9285F8D9C36 15:50:06.293 "No device setup found" 15:50:06.294 Deselected device

I cannot exactly reproduce which steps solved the issue for me but anyone with the same issue might want to try this exercise I went through with the help of ChatGPT:

a) the PPK2 hardware seems to show up as COM-Port AND as PPK2 device. Check in device manager ("Geräte manager") for the COM Port and device PPK2. This is the screenshot with a properly working setup - initially I only saw COM14.

The serial device will use usbser.sys, not an issue in my installation. But a device "PPK2" showed up under "other devices" and an issue due to some inappropriate driver. You may see errors in the event log for this device:

ChatGPT was focusing on the MI_00 device not being properly recognized.

Not sure which of the following steps did actually resolve the issue:

b) select another device driver for this "broken" device - I asked to chose from the list and selected something like SEGGER-WinUSB. The error message was gone with the device working properly but the power profiler was still unhappy (same error message)

or c) uninstall/delete this device (keep the COM-Port, that wasn't the issue with me and ChatGPT recommended not to touch it)

d) then I uninstalled the power profiler (from nrf connect) AND uninstalled nrf connect (from Windows). Not sure if b) or c) makes the difference

e) maybe reboot here

f) re-installed nrfConnect WITH ADMIN RIGHTS and then re-installed power profiler within nrfConnect

Now power profiler instantly popped up saying "Device needs to be programmed" and after letting it flash the PPK2 hardware it switched its color to white

So the root cause is windows installing the wrong driver for the PPK2 hardware when first plugged in and Power Profiler will then not detect it properly (maybe see some of it through the com port, like the serial number). That's why plugging it into a hub or another USB-Port might help as Windows might re-install the (this time proper) driver for the PPK2.

At some point I also removed the "broken" PPK2 device entry in device manager - maybe this plus re-installing nrfConnect from scratch might do the job too or was also important in my case.

In a nutshell: check in device manager if your "PPK2" device is under the "broken" devices/devices with errors (Error 28 in my case). You need to somehow fix this by either setting the proper device driver (Segger WinUSB or alike) or by forcing windows to re-install it with the right one.

Also: maybe always install nrfConnect first, then plug the PPK2 hardware? This might help getting the right device driver installed in the first place?

Right now I cannot find a separate "PPK2" device entry in Device manager anymore. Also this device seems to belong to the solution as it disappears when unplugging the PPK2:

Sorry for this not being a proven straightforward instruction but rather a list of hints re. the root cause.