• State Not Answered
  • Replies 12 replies
  • Subscribers 63 subscribers
  • Views 1818 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 296349
Options

Issue with Actinius Programmer detecting Icarus?

Account01

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

  • 0 in reply to Einarh

     


    Yes, I tried even doing a dpkg -r and then a dpkg -i and manually copying the udev file (from github) to the rules directory and rebooting the machine in case my udev restart was not working correctly.

  • 0 in reply to Account01

    Hm, starting to sound like an issue with this Actinius software specifically.

    Have you contacted the people who maintain it?

  • 0 in reply to Einarh

     
    No, I asked them a different question via github. They answered my question but urged that future questions should be brought up here.

    I started to hedge my bets and bought a jtag cable from Tag-connect (TC2030-CTX-NL for 10-pin "no legs" needle/pogo probes) and a NRF5340-DK (to use their onboard J-Link interface since JLink devices are either too expensive or out of stock) because those were the two cheapest options to do a JTAG firmware upload to bypass any mcuboot handshaking issues.
    Delivery was pretty fast, so hopefully this will fix it over the weekend.

    Is there a way to contact the dev team for the Actinius Programmer?

    Thanks!

  • 0 in reply to Account01

    I would suggest asking them on github. If the issue is with their programmer software, then this is not the place to bring it up.

    Their github also links to a website and a support email.

    I hope your JTAG approach is successful.

    Best regards,

    Einar

  • 0

    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.

Related