Issue with Actinius Programmer detecting Icarus?

I was running Ubuntu 18.04 and Actinius Programmer was able to upload an example firmware without a problem. However, I upgraded my computer to Ubuntu 20.04 and Actinius Programmer now refuses to recognize my Icarus board. Here is my environment:

Here's a screen shot of the device labelled as "Unknown" and not being recognized with "vid: 0xundefined, pid: 0xundefined"

Edit: Here's the full error

  • Continuing on, here is the lsusb:

    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 062a:727a MosArt Semiconductor Corp. Full-Speed Mouse
    Bus 001 Device 021: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
    Bus 001 Device 006: ID 8087:0aaa Intel Corp.
    Bus 001 Device 005: ID 0bda:5539 Realtek Semiconductor Corp. Integrated_Webcam_HD
    Bus 001 Device 004: ID 0a5c:5842 Broadcom Corp. 58200
    Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    And this is the dmesg when I plug in:

    [ 9335.169573] usb 1-2: new full-speed USB device number 21 using xhci_hcd
    [ 9335.325348] usb 1-2: New USB device found, idVendor=0403, idProduct=6015, bcdDevice=10.00
    [ 9335.325352] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 9335.325355] usb 1-2: Product: Icarus (nRF9160)
    [ 9335.325358] usb 1-2: Manufacturer: Actinius
    [ 9335.325360] usb 1-2: SerialNumber: AC5RG3VE
    [ 9335.332169] ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected
    [ 9335.332440] usb 1-2: Detected FT-X
    [ 9335.333728] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0
    [ 9335.333816] usb 1-2: authorized to connect

    When I do the Reset and user button dance (Hold reset, hold P5, release reset, release P5) I don't see anything in dmesg, and it is still "Unknown" in Actinius Programmer.

    I currently have dialout group privileges, which is the group member that /dev/ttyUSB0 is in.

  • Hello

    have you tried installing JLink v7.66a instead of v7.80c as suggested by your error log?

    Best regards


  • I didn't understand what that meant... I'll try downgrading. 

  • Unfortunately that did not help. The log file shows the following:

    2022-10-04T18:17:54.316Z ERROR Unsupported device.
                The detected device could not be recognized as
                a JLink or an Actinius device. (vid: 0xundefined, pid: 0xundefined)
    2022-10-04T18:17:54.316Z ERROR Please make sure J-Link Software and actinius-usb-udev rules are installed. See

    I think what might have happened is the last firmware I uploaded was a build/zephyr/merged.hex, would that cause issues with the mcuboot function? I assumed that was the one I needed to upload because west build in VS Code ended with that after compilation.

  • Have you installed Actinius USB udev rule from github again after upgrading Ubuntu?