New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the Reset & Restart functionality (IEP-1177) #907
Comments
Hi @LemonBoy, Thank you for reporting this and sorry for the delayed response. Have you tried this button? It restarts debug without terminating and relaunching. It's also available from the right-click on the debug thread action: |
Well, it turns out that Eclipse removed that button from the toolbar a while ago. No idea why it's still present in your Eclipse install. From the plugin side it should be quite easy to add back the button into the debug toolbar, the action name is |
Hi @LemonBoy, Thank you for the info. I didn't know this command wasn't enabled by default. I probably have it because I accidentally installed additional (optional) packages from CDT Eclipse via the update site. We will include this command by default. By the way, thank you for pointing out that the Espressif-IDE version is not updated in the online installer. It looks like PR is already there and will be merged soon. Here are options that you can use now to get the latest Espressif-IDE version:
|
Hi @LemonBoy, I found which plugin update has I tested it by installing the latest version of Espressif-IDE and after updating this plugin, this action appeared in the toolbar |
Thanks for the feedback, after installing the updated Shall I close the issue? Or do you still plan on doing something related to this? |
Hi @LemonBoy, We are planning to make this action available out of the box. Until then, let's keep this issue open. Thank you. |
Some other IDEs by other uC vendors include a "Reset & Restart" button allowing the devloper to restart both the uC and the debugging session without having to reflash the image every time.
Under the hood the command is simply sending a
monitor reset
command to the GDB instance the debugger is attached to, AFAICT the OpenOCD/GDB interface is already working but issuing that command from the "Debugger Console" confuses the debugger.The text was updated successfully, but these errors were encountered: