No device with extension nRF Connect VS Code (Windows)

RE: No device with extension nRF Connect VS Code (Windows)

runsiv — Tue, 07 Feb 2023 14:50:00 GMT

I think this case might be helpful for you

nRF9160 with Microsoft Azure, x509 certificates and provisioning methods, TLS store write wear

If you have more questions about mqtt and x509 please open a new ticket so that the correct person will be assigned to the case.

Cheers

Runar

RE: No device with extension nRF Connect VS Code (Windows)

Lukas Mertens — Tue, 07 Feb 2023 13:35:54 GMT

Thanks, that worked!

Is there any example using x509 certificate to a mqtt broker? can't find one.

RE: No device with extension nRF Connect VS Code (Windows)

runsiv — Tue, 07 Feb 2023 10:23:50 GMT

Hi, I need to look into the first problem to try to recreate it. However I would recommend doing a pristine build if you change board

In order to create the app_signed.hex you need to add support for MCUboot in your project as it not by default in this example

in order to do it, add CONFIG_BOOTLOADER_MCUBOOT=y in your prj.conf

Regards

RE: No device with extension nRF Connect VS Code (Windows)

Lukas Mertens — Tue, 07 Feb 2023 09:19:22 GMT

Oke that is true, the files definitly are there. But now my next problem 😃

When i'm trying to build my mqtt-simple program, there is no "actinius_icarus_ns" board anymore like in the hello_world sample. I can select the icarus board when i push on Nodic board but then got an error:

When i try to build with the only compatible board i don't get the "app_signed.hex" file in the zephyr folder.

RE: No device with extension nRF Connect VS Code (Windows)

runsiv — Tue, 07 Feb 2023 09:02:57 GMT

Hi,

If you ctrl+click on the squiggly lines, will it jump to the correct file? If not you need to add the path for the ncs 2.2.0 folder for intellisense

Sometimes it's just intellisense that is reporting false errors.

RE: No device with extension nRF Connect VS Code (Windows)

Lukas Mertens — Tue, 07 Feb 2023 08:50:23 GMT

Hi,

When I’m opening my mqtt-simple sample I get some error’s that they don’t find any file.

I installed the nRF connect sdk using the toolchain manager (2.2.0).

How can i fix this?

RE: No device with extension nRF Connect VS Code (Windows)

runsiv — Tue, 07 Feb 2023 07:35:43 GMT

Hi,

The files should be located in "projectfolder/build/zephyr/" after you have built your project.

Regards

Runar

RE: No device with extension nRF Connect VS Code (Windows)

Lukas Mertens — Tue, 07 Feb 2023 07:03:41 GMT

Yeah, already saw that, but i don't find the files they called to write

RE: No device with extension nRF Connect VS Code (Windows)

runsiv — Mon, 06 Feb 2023 17:19:49 GMT

Hi Lukas

Please see https://docs.actinius.com/getting-started/flashing-an-application#flashing-an-application-using-the-actinius-programmer

Regards

Runar

RE: No device with extension nRF Connect VS Code (Windows)

Lukas Mertens — Mon, 06 Feb 2023 15:22:35 GMT

So i need to build my programm into SV Code and than upload it into "Actinius Programmer"?

Which file do i need to upload? They said a .hex file but i don't know where to find the right one

RE: No device with extension nRF Connect VS Code (Windows)

Turbo J — Mon, 06 Feb 2023 15:16:53 GMT

Normal behavior.

The IoT board does not ship with a SEGGER debugger unlike the NRF5x DKs. You need the "Actinius Programmer" in order to access the device.