• State Not Answered
  • Replies 14 replies
  • Subscribers 88 subscribers
  • Views 1281 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 358112
Options

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

Parents
  • 0

    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

Reply
  • 0

    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

Children
No Data
Related
Terms of service