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

[jdub]

Hi,

On Ubuntu, after a distribution upgrade from 22 to 24, NRFConnect has failed in a couple of ways.

1. Upon starting, the application fails with:

[7982:0910/180010.628514:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_nrfconpXV1A2/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

I found a couple workarounds for this, the easiest is to just run nrfconnect with the --no-sandbox option. So I don't have a question about this issue, I'm just raising it with the hope it will be fixed in the next version.

2. The thing that's stopping me right now is that when I try to connect to the PPK2 from the Power Profiler app version 4.2.0, the software gives me "No device setup found". A more complete log is posted below.

18:45:14.338    Initialising nrfutil module: device
18:45:15.635    Using nrfutil-device core version: 7.13.0
18:45:15.854    Using nrfutil-device version: 2.3.5
18:45:15.854    Using nrf-device-lib version: 0.17.17
18:45:15.854    Using nrfjprog DLL version: 10.24.0
18:45:15.854    Using JLink version: JLink_V7.94e
18:45:16.712    Device Connected SN:000609303003
18:45:16.713    Getting serialport options from persistent store 000609303003.pc-nrfconnect-ppk
18:45:16.714    Device Connected SN:E18A6F482602
18:45:16.714    Getting serialport options from persistent store E18A6F482602.pc-nrfconnect-ppk
18:45:22.967    Error: Failed with exit code 1. Failed to device info one or more devices: * E18A6F482602: [sdfu] No deviceInfo available for the device, code: Argument. Message: Operation device-info failed, [sdfu] No deviceInfo available for the device.
18:45:22.968    Validating firmware for device with s/n E18A6F482602
18:45:22.968    Connected to device with serial number: E18A6F482602 and family: Unknown
18:45:22.968    Note: no pre-compiled firmware is available for the selected device.
18:45:22.969    Error while setting up device E18A6F482602
18:45:22.969    "No device setup found"
18:45:22.969    Deselecting device

I am on a dual-boot machine and can connect to the PPK2 from NRFConnect in Windows 11. So I know the USB port, cable, and PPK2 firmware are OK. The same version of power profiler (4.2.0) is in use for both operating systems.

Does anybody have any ideas for how to get around this? It's a major snag in my development workflow.

Thank you!

[Toastus]

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

[jdub]

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.

[jdub]

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