Debugging in Eclipse requires restart to run properly?

[Dave_couling]

Since I've migrated to SDK 10 and updated all my toolchains I've noticed that when I debug on Eclipse, when I run my code nothing happens properly. However if I pause and restart the code code everything works properly. I'm 99% sure its just an issue with one of the NRF tools I updated and Eclipse. But wanted to ask on here. Has anyone seen this issue where you must run -> restart -> run in order to get your code to execute properly on Eclipse?

Thanks for the help guys,

DC

[Vidar Berg]

It sounds like the debugger is not resetting the device properly upon connection. Is "initial Reset and Halt" enabled in your debug launcher?

Update 5/10

The debug launcher is only using the segger drivers so I would suggest to try updating to the latest Segger drivers, and make sure that the debug launcher is pointing to this version:

[Dave_couling]

Yes this items are checked in my Debug Configuration. I wonder if this has anything to do with the fact nRFStudio seems to be crashing alot more with the last update.

[Dave_couling]

I understand about how the debugger only uses the Segger driver. I just hypothesized that the fact that nRFStudio becoming a bit unstable with the latest Segger driver this may also be applying to the Eclipse GCC debugging.

[Vidar Berg]

Agree with your reasoning, they are both using the same drivers. However, the driver available on Segger.com is ahead of the version included in nrfgo studio so I think it's worth trying to update.