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

Parents
  • This is for future users that have encountered the same problem... but just to document, here's the JLink error I got after trying JLink:


    2022-10-10T23:08:06.320Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
    2022-10-10T23:08:06.320Z INFO Loading readback protection status for Application core
    2022-10-10T23:08:06.509Z ERROR Failed to load readback protection status: protection-get operation not supported
    2022-10-10T23:08:06.509Z ERROR This is an issue with nRF Connect for Desktop (Core).
    2022-10-10T23:08:06.509Z ERROR Please restart Actinius Programmer while keeping JLink connected to your device.
    2022-10-10T23:09:36.132Z INFO Target device closed

    This is rather unfortunate, seems like it's hung up on trying to get readback protection status?

    I'm using the nRF5340-DK JLink interface, and the tag-connect TC2030-CTX-NL cable. The Actinius Programmer found the JLink interface fine, but (I'm guessing) in attempting to graph out the memory map, it errored out.

    edit: According to another post about readback protection status error, I tried nrfjprog --recover and it wouldn't detect my Jlink debugger.

    $ nrfjprog --recover --log
    ERROR: No debuggers were discovered.

Reply
  • This is for future users that have encountered the same problem... but just to document, here's the JLink error I got after trying JLink:


    2022-10-10T23:08:06.320Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
    2022-10-10T23:08:06.320Z INFO Loading readback protection status for Application core
    2022-10-10T23:08:06.509Z ERROR Failed to load readback protection status: protection-get operation not supported
    2022-10-10T23:08:06.509Z ERROR This is an issue with nRF Connect for Desktop (Core).
    2022-10-10T23:08:06.509Z ERROR Please restart Actinius Programmer while keeping JLink connected to your device.
    2022-10-10T23:09:36.132Z INFO Target device closed

    This is rather unfortunate, seems like it's hung up on trying to get readback protection status?

    I'm using the nRF5340-DK JLink interface, and the tag-connect TC2030-CTX-NL cable. The Actinius Programmer found the JLink interface fine, but (I'm guessing) in attempting to graph out the memory map, it errored out.

    edit: According to another post about readback protection status error, I tried nrfjprog --recover and it wouldn't detect my Jlink debugger.

    $ nrfjprog --recover --log
    ERROR: No debuggers were discovered.

Children
Related