NRF Power Profiler Kit 2 (PPK2) won't connect: "No device setup was found"

RE: NRF Power Profiler Kit 2 (PPK2) won't connect: "No device setup was found"

jumper384 — Mon, 13 Jan 2025 11:40:20 GMT

hello. this was the first link for this problem so i thought i'd reply here for any body else.

what's worked for me in this case is adjusting your udev usb rules.

in terminal, find your usb details with `lsusb`

Bus 001 Device 014: ID 1915:c00a Nordic Semiconductor ASA PPK2

then create a udev rule for usb in /etc/udev/rules.d/99-usb.rules

edit that file so you enter the following:

SUBSYSTEM=="usb", ATTR{idVendor}=="1915", ATTR{idProduct}=="c00a" MODE="0666", GROUP="dialout"

NOTE, the idVendor and idProduct is device specific and can be inferred by the lsusb output. the rest you may copy.

reload the rules and you're good:
sudo udevadm control --reload-rules
sudo udevadm trigger

RE: NRF Power Profiler Kit 2 (PPK2) won't connect: "No device setup was found"

jdub — Wed, 11 Sep 2024 18:02:07 GMT

Just reporting that I have a viable workaround by setting up a chroot environment running Ubuntu 22 with debootstrap. Within the chroot I had to install a couple packages I couldn't find in apt to run nrfconnect, like libfuse2, but other than that it wasn't too bad. Now that it's set up I just need to bind the relevant files and tell X to accept local connections and it works. Here's my script for starting up the environment now:

#!/bin/bash

echo "Mounting required directories..."

sudo mount --bind /proc /srv/ubuntu22_chroot/proc
sudo mount --bind /sys /srv/ubuntu22_chroot/sys
sudo mount --bind /dev /srv/ubuntu22_chroot/dev
sudo mount --bind /dev/pts /srv/ubuntu22_chroot/dev/pts
sudo mount --bind /tmp/.X11-unix /srv/ubuntu22_chroot/tmp/.X11-unix

xhost +local:

echo "Entering chroot..."

sudo chroot /srv/ubuntu22_chroot

export DISPLAY=:0
xauth add my_pc/unix: MIT-MAGIC-COOKIE-1 XXXXXXXXXXXXXXXXXXXXXXXXX

RE: NRF Power Profiler Kit 2 (PPK2) won't connect: "No device setup was found"

jdub — Wed, 11 Sep 2024 16:18:37 GMT

Thanks Toastus, you're right I probably updated too early. My enthusiasm for the latest and greatest overcame my senses. Your idea for a chroot is good, I will give it a shot as a stop-gap measure and report back. In the mean time I hope my report helps the Nordic folks make their updates.

RE: NRF Power Profiler Kit 2 (PPK2) won't connect: "No device setup was found"

Toastus — Wed, 11 Sep 2024 02:09:24 GMT

In case you didn't notice, Ubuntu 24 is not officially supported yet by the nrf SDK tools. I got similarly burned by upgrading to 22 too early. If you don't want to (or cannot) roll back to 22, have you tried running under an Ubuntu 22 chroot?

Chroot doesn't always fix everything, but chroot has saved me a few times with exactly this issue. In the past, I have invoked the under a chroot command line, but it's been a while. Examining the command line of a running instance of one of the other tools should give you the necessary syntax. If you can then invoke the PPK2 tool that way (or else, indirectly by launching the main NRF Desktop app first), it may get you across the line while waiting for the devtools to catch up.

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/installation/recommended_versions.html#supported-os