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

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!

Parents
  • 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

Reply
  • 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

Children
No Data
Related