Incorrect Jlink behavior on Mac OS in VSCode

[Alexander Koval]

Hi there!

I'm having trouble debugging a small project using the xiao nrf52840 board and the J-Link debugger. Everything works fine on Windows, but on Mac OS, the debugger only starts once. The second time, it returns an error message saying "failed to initialize the CPU module in the firmware because the probe is low on memory". Reconnecting the probe fixes the issue, but it reoccurs in the next debugging session.

Debugging with Ozone works fine on the same machine. I have found suggestions online that this issue may be caused by an incorrect termination of the debug session. Is there any configuration related to J-Link that could be causing this problem, or any other ideas on how to fix it?

I'm using OSX 15.7.2, J-Link software 8.9.6 and J-Link V8.

Any suggestions would be greatly appreciated.

[Susheel Nuguru]

Hi Alexander, 

Hard to suggest something without being able to reproduce the issue at my end. This either seems like an issue with Segger driver or VSC extension. Can you see if some of the suggestions mentioned in this helps? or try rolling back to older segger driver versions.

[Alexander Koval]

Hi, thanks for the reply.
No difference on the previous version of the driver. I'm pretty sure this is a problem with the vscode extension. I have found reports on the Internet about exactly the same error in Linux+Jlink+VSCode, regardless of Nordic.
I guess I'll have to put up with it and debug everything in Ozon. It's still a hobby project, so it's okay. And my jlink is pretty old and lousy, left over from an old project from ten years ago.

[Susheel Nuguru]

Thanks for letting us know about that. Yes, Ozone is not bad to debug with when you can build everything in VSC and start the debugging with Ozone with just one click from the VSC.  Yes the UI and keyboard shortcuts of Ozone are a bit different than VSC, but we can still debug :)