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

[Benjamin]

Hi Alberto,
What JLink version do you see this at? Do you still get the error messages if you downgrade?

Best regards,
Benjamin

[albert_1977]

Hi Benjamin,

It's with version 9.26. I will try an older version.

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

[ct0]

I can confirm this issue is happening with v9.26, and doesn't happen with older v8.x versions.

[Benjamin]

Hi,

I was able to reproduce the issue, V9.14a is the earliest version where it appears. It does not seem to affect the actual functionality. Please note that this occurs only when using nrfjprog, not nrfutil, which is the current supported tool. The nrfjprog tool was removed as of nRF Connect SDK v2.8.0.

Anyways, thanks for the reports! I will forward it internally.

Best regards,
Benjamin