Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 535163 - GDB Hardware Debugging launch should use "reset and halt" command where available
Summary: GDB Hardware Debugging launch should use "reset and halt" command where avail...
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-hardware (show other bugs)
Version: 9.4.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 9.9.0   Edit
Assignee: John Dallaway CLA
QA Contact: John Dallaway CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 550963
  Show dependency tree
 
Reported: 2018-05-27 08:19 EDT by John Dallaway CLA
Modified: 2019-09-11 06:03 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Dallaway CLA 2018-05-27 08:19:12 EDT
When a GDB Hardware Debugging launch is configured to reset the hardware and halt without delay, the launch sequence should issue reset and halt as a single command where this is supported by the GDB server implementation. This will require a new IGDBJtagDevice.doResetAndHalt() method which is invoked only when both reset and halt are enabled with zero delay. The default implementation should fall back to using two commands.
Comment 1 Eclipse Genie CLA 2019-08-23 10:49:30 EDT
New Gerrit change created: https://git.eclipse.org/r/148243
Comment 3 Eclipse Genie CLA 2019-08-23 14:48:44 EDT
New Gerrit change created: https://git.eclipse.org/r/148250