At Jumper we’re developing tools that increase the happiness levels of embedded software developers. Our main tool to date is the Jumper Emulator. As a part of the development process we’re required to use embedded debuggers to verify that our emulator is on par with the actual hardware. Our focus is on ARM Cortex M devices. The MCUs we’re debugging are the nRF52, STM32F4 and LPC1768.
An Embedded software debugging session can get quite frustrating. After testing several options, we’re happy to provide a summary of what we learned. Let us know if we missed something! (firstname.lastname@example.org).
Here are the results - https://medium.com/jumperiot/debuggers-for-embedded-how-to-choose-the-right-debugger-a727b33b4061
Actually, I'm using Eclipse and Visual Studio Code on a Mac and also on Ubuntu 16. I may have found a solution to the stability issues I experienced with Eclipse and will update soon.
The conclusion is probably quite good for anyone using Windows, VisualS isn't bad.
Would be good to see a roundup of debugging environments for those of us on other operating systems.
There are other article on Eclipse GCC & debugger with multiple MCU. See links bellow
Eclipse with nRF5x : embeddedsoftdev.blogspot.ca/.../ehal-nrf51.html
JTag debugger : embeddedsoftdev.blogspot.ca/.../idap-link.html
Multi-architecture hardware abstraction library : embeddedsoftdev.blogspot.ca/.../h.html
MCU tested : LPC17xx, LPC11xx, KL26Z, nRF5x, CC3200