nRF Connect VS Code Extention

[Emre Bayraktar]

I'm having an issue while trying to install the nRF Connect vsCode extension. I assume that extension has auto board detection feature. However, on my computer, this feature does not work as expected. There is another device connected to my computer which opens a couple of virtual com ports. When I enable the nrf extension, it continuously opens and closes these com ports, making them unusable. How can I disable the auto-board-detection feature ? 

[Emre Bayraktar]

Hi, 

Sorry for the confusion. I've successfully installed and uploaded code to nrf54L devkit. I'm also doing development on  Quectel's SoC's which connected via USB and creates seven virtual com ports for different purposes. I meant the Quectel's SoC by "another device". 

The problem arises when I plug in the Quectel device while the nRF Connect extention is enabled. Once connected, extention continuously opens and closes the com ports of Quectel SoC. Since its automatically does this open/close behaviour, I've assumed that nRF connect continously search through avaiable com ports to find a nrf board.

[Emre Bayraktar]

Hi, 

The problem continues even if I plug in a Nordic device. I've confirmed the open/close behaviour caused by extention since it only happens when VS Code is open and extention enabled. In this state, I cannot use the Quectel's com ports with any application. When I disable the extention, open/close behaviour immediately stops and com ports became usable. 

[dejans]

Hi,

Is this issue reproducible just by running "nrfutil device --hotplug"?

Best regards,
Dejan

[Emre Bayraktar]

Hi, 

The command returned error. Here is the output: 

PS C:\ncs\v3.1.0\zephyr\samples\basic\blinky\build\blinky> nrfutil --version
nrfutil 8.1.0 (34e21a1 2025-07-29)
commit-hash: 34e21a1552aac39ed806b758e291c32039a54754
commit-date: 2025-07-29
host: x86_64-pc-windows-msvc
build-timestamp: 2025-07-29T10:51:28.573982200Z
classification: nrf-external

PS C:\ncs\v3.1.0\zephyr\samples\basic\blinky\build\blinky> nrfutil device --hotplug
error: unexpected argument '--hotplug' found

Usage: nrfutil device [OPTIONS] [COMMAND]

For more information, try '--help'.
PS C:\ncs\v3.1.0\zephyr\samples\basic\blinky\build\blinky>

Best regards, 

Emre

[dejans]

Hi Emre,

I have noticed that "list" was missing from suggested command. I apologize for this. Correct command is "nrfutil device list --hotplug". Is your issue reproducible using this command?

Best regards,
Dejan

[Emre Bayraktar]

Hi Dejan,

I've noticed it and tried with "list" command. It did not reproduce the issue. This command can detect the connected nrf devkit. But when I connect the Quectel device, open/close behaviour continues. 

Best regards, 

Emre. 

[dejans]

Hi Emre,

Can you try to run the command shown below?

nrfutil device device-info --serial-number <SN_from_nrfutil_device_list>

What is the result?

Best regards,
Dejan

[Emre Bayraktar]

Hi Dejan, 

Here is the output: 

PS C:\Users\A.ogur> nrfutil device list --hotplug
1057715871
Product         J-Link
Board version   PCA10156
Ports           COM143, vcom: 0
                COM142, vcom: 1
Traits          jlink, devkit, usb, serialPorts, seggerUsb, boardController

Supported devices found: 1

^S
PS C:\Users\A.ogur> nrfutil device device-info --serial-number 1057715871                   
serial_number: 001057715871        
        boardVersion: PCA10156     
        deviceFamily: NRF54L_FAMILY
        deviceName: nRF54L15       
        deviceVersion: NRF54L15_xxAA_REV1
        jlinkObFirmwareVersion: J-Link OB-nRF5340-NordicSemi compiled Feb 11 2025 17:15:35

PS C:\Users\A.ogur> 

Best Regards,

Emre.

[dejans]

Hi Emre,

Did running "nrfutil device device-info --serial-number 1057715871" also cause "..., it continuously opens and closes these com ports, making them unusable"?

Best regards,
Dejan

[Emre Bayraktar]

Hi Dejan, 

The problem starts happenning as soon as I open the VS Code while the Quectel device is connected via USB. And when I disable the nRF Connect extention, it stops happening. So I can not tell you whether the problem can be created by that command or not. 

Best Regards, 

Emre.