VS Code: SeggerBackend jlinkarm.dll reported error at line ...

[albert_1977]

Hi all,

I recently updated all Segger JLink software using the Segger download links and updated the probe as prompted by VS Code NRF Extension. Up until about two days ago, before the updates, flashing worked very well and without issues.

Since today, I get the following errors on screen:

It seems though that the flashing does work correctly, because the firmware gets updated on an NRF52840 (u-Blox Module) custom board.

Additionally, the VS Code extension now recognises an STM32 debugger, which didn't happen up until yesterday or two days ago.

Any ideas what it may be?

Cheers,

Alberto

[albert_1977]

So, I downgraded to v8.20 which is 1 year old, that doesn't show the error message anymore.

I still get both debuggers showing in VS Code however, and each time I need to choose which one I can use:

Is there a way for the flasher to remember which one it uses by default?

Thanks for your help so far.

Cheers,

Alberto

[Benjamin]

Could you do nrfutil device list and paste the output?

[albert_1977]

>nrfutil device list
001E000C5553500C20393256
Product STLINK-V3
Ports COM4
Traits serialPorts, usb

603005698
Product J-Link
Traits usb, jlink, seggerUsb

Supported devices found: 2

This is ok, I have both devices connected. I'd just like to have the J-Link as default when flashing and not having to select it each time.

Also, both nrfprog and nrfutil are installed. As far as I know, I'm working with nrf connect SDK v3.11, but I can't find where to check the version.

Thanks for your help so far.

[Benjamin]

Hi,
This should be possible. Try filling in the snr field in launch.json. Please see:

How to customize launch and debug configurations

Custom launch and debug configuration fields