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,

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

[Tommy F Kristensen]

Hi I Benjamin

I can see that you forwarded this internally for 3 months ago, I still have this issue on my SDK 3.0.2  with the latest version of Jlink.

Do you know if there are found any solution oin the errors

Best Regards 

Tommy F Kristensen

[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 736.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 629.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 3139.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 911.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 3139.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 3139.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 3139.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 3087.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 3112.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 3349.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 3160.
[error] [SeggerBackend] - JLinkARM.dll reported error -256 at line 3176.
[error] [ Client] - Encountered error -102: Command read_device_info executed for 139 milliseconds with result -102
[error] [ Client] - Encountered error -102: Command read_memory_descriptors executed for 31 milliseconds with result -102

[Elfving]

Hi Tommy,

Are you seeing this with nrfutil too? Note that nrfutil is the recommended tool going forward.  
Have you changed what tool you are using to flash in the background? This should default to nrfutil in NCS >=3, and I thought this issue would only appear with nrfjprog.

Did you also upgrade JLink to whichever was newest? We recommended a certain version which came alongside nrf command line tools. 

Regards,

Elfving