Issue with Actinius Programmer detecting Icarus?

RE: Issue with Actinius Programmer detecting Icarus?

Einarh — Tue, 11 Oct 2022 07:43:58 GMT

Perhaps try the nrf udev rules:

https://github.com/NordicSemiconductor/nrf-udev

-Einar

RE: Issue with Actinius Programmer detecting Icarus?

Account01 — Mon, 10 Oct 2022 23:30:23 GMT

Thanks! I just tried to use JLink (the cable and nrf5340 DK arrived two days ago) and it still doesn't detect the Icarus, so I'll have to email the developers what corner case I got myself into.

RE: Issue with Actinius Programmer detecting Icarus?

Account01 — Mon, 10 Oct 2022 23:30:05 GMT

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.

RE: Issue with Actinius Programmer detecting Icarus?

Einarh — Mon, 10 Oct 2022 09:02:47 GMT

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

RE: Issue with Actinius Programmer detecting Icarus?

Account01 — Fri, 07 Oct 2022 15:11:41 GMT

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!

RE: Issue with Actinius Programmer detecting Icarus?

Einarh — Thu, 06 Oct 2022 09:19:56 GMT

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

Have you contacted the people who maintain it?

RE: Issue with Actinius Programmer detecting Icarus?

Account01 — Wed, 05 Oct 2022 15:44:09 GMT

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.

RE: Issue with Actinius Programmer detecting Icarus?

Einarh — Wed, 05 Oct 2022 07:47:38 GMT

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

RE: Issue with Actinius Programmer detecting Icarus?

Account01 — Tue, 04 Oct 2022 18:24:57 GMT

Einarh 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 https://github.com/actinius/actinius-usb-udev

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.

RE: Issue with Actinius Programmer detecting Icarus?

Account01 — Tue, 04 Oct 2022 18:13:43 GMT

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

RE: Issue with Actinius Programmer detecting Icarus?

Einarh — Tue, 04 Oct 2022 14:37:52 GMT

Hello

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

Best regards

Einar

RE: Issue with Actinius Programmer detecting Icarus?

Account01 — Mon, 03 Oct 2022 21:45:49 GMT

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.