actinius icarus only registers as ftdi serial device (vendorid 0403, productid 6015)

[gnssr-dev]

I just bought an actinius icarus board, and am trying to connect to it on linux (or windows),

The problem is that when I plug in the board in the usb, it will only appear as a ftdi serial port

lsusb mentions:

Bus 001 Device 029: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)

I was actually expecting jlink interfaces with sometthing like:

Bus ... Device ..: ID 1366:.... SEGGER 

The same happens when I check the port in a windows vm (and on another windows computer): no jlink ports are appearing under the COM ports.

Furthermore:

I can flash a prebuild app from the windows vm (but not from linux, as the device is not recognized), but only using mcuboot, so I don't see a way to change the mcuboot itself.

I  managed to build a few sample apps for the board and tried flashing them through the windows vm version of "actinius programmer", but none of them seems to work.

Any hints of where to start?

[Albrecht Markus Schellenberger]

Hello,

Any hints of where to start?

You could try to flash one of the provided prebuilt application firmware images to your board using the Actinius Programmer, as described here. Otherwise, if you want your device to be detected via a COM port, you need a nRF9160 DK or J-Link Mini EDU for programming.

Regards,

Markus

[gnssr-dev]

Thanks, I think I'm starting to get the idea now, so the device will only expose a jlink port after flashing an appropriate system through the jtag pins?

Flashing a prebuilt image works (and the app works) through "actinius programmer" via windows VM. I still need to  figure out how to get this working in linux as nrfconnect doesn't recognize the board there.

Is there a way to flash the prebuilt hex files from the command line in linux? Mcumgr seems to work in linux but I only have the hex versions of the prebuilt applications.