Ozone VS code debugger is not working

RE: Ozone VS code debugger is not working

Edvin — Fri, 12 Jan 2024 09:35:51 GMT

Sorry for the late reply. I have been out of office. Please try updating the Ozone version, as suggested by dyoung.mpd . This may update the drivers used by Ozone, and hopefully they will match your new JLink versions. Let me know if it doesn't work.

Best regards,

Edvin

RE: Ozone VS code debugger is not working

dyoung.mpd — Thu, 11 Jan 2024 22:08:57 GMT

I had the same core support plugin error in Ozone after updating nRF Connect for Desktop and the Segger driver files.

Updating Ozone from V3.30c to V3.30d fixed the problem for me.

I hope this helps,

Doug Young

RE: Ozone VS code debugger is not working

vim_nordic — Mon, 08 Jan 2024 06:17:18 GMT

Hi Edvin ,

My setup is working fine, I am able to build, flash and run the code on devices as well.

I am facing the issue after nRF Connect for Desktop upgrade to latest version of 3.4.0. Which has upgraded the supported drivers as well.
As per my understanding, after upgrading the supported library from nRF Connect for Desktop, it is giving some problem in integration of ozone and setup library.

Thanks & Regards

Vimal Verma

RE: Ozone VS code debugger is not working

Edvin — Thu, 04 Jan 2024 14:12:15 GMT

Hello,

Can you check whether Visual Studio code is set up with the correct toolchains and workspace?

It doesn't need to be 2.5.0, but they should match up.

BR,
Edvin

RE: Ozone VS code debugger is not working

vim_nordic — Thu, 04 Jan 2024 09:49:22 GMT

Hi Edvin ,

Thanks for your response.

I have tried to debug on nRF Connect SDK v2.4.1 as well, But facing the same issue after nRF Connect for SDK application auto update to version v4.3.0.

I think some drivers got updated along with nRF Connect for Desktop application, Due to this happening. Not I am able to see the 2 Jlink driver version in my install list as Jlink V7.80c (32 Bit windows) and Jlink V7.88j ( 64 Bit Windows ). Due to this it is not picking correct core.

Please suggest how to fix this.

Regards

Vimal Verma

RE: Ozone VS code debugger is not working

Edvin — Wed, 03 Jan 2024 14:38:19 GMT

Hello Vimal,

Does this happen to all the applications that you test from v1.9.1? Does it also happen if you try a sample after v2.0.0? I tested a couple of sample applications from v1.9.1, but I am not seeing the same as you are seeing.

Is the zephyr.elf file present at the point in time when you press "Debug with Ozone"?

Best regards,

Edvin