diff options
| author | Tim Newsome <tim@sifive.com> | 2020-06-18 14:47:42 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-18 14:47:42 -0700 |
| commit | 03f943ae239f59727ef47e46fffc31dd405a642d (patch) | |
| tree | 8eee5a0325c7bfec757c6b6e5d310cff8aee5272 /tools | |
| parent | 3c6592cf6216225a934eafd45ad9f320ab7c7fc6 (diff) | |
| download | riscv-openocd-03f943ae239f59727ef47e46fffc31dd405a642d.zip riscv-openocd-03f943ae239f59727ef47e46fffc31dd405a642d.tar.gz riscv-openocd-03f943ae239f59727ef47e46fffc31dd405a642d.tar.bz2 | |
Step/resume off manual hardware triggers (#486)
* Accommodate users setting custom triggers.
RISC-V hardware supports many more triggers than gdb can communicate to
OpenOCD. Accommodate users that set triggers by writing tdata* directly,
by disable/step/reenable when a user has done that.
Note that users must set dmode in tdata1 for this behavior to work
properly. Triggers with dmode=0 are assumed to be set and handled by the
software that is being debugged.
Change-Id: Ib0751689c5553aae3a273395b10f5b98326fa066
* Enumerate triggers when resuming from a trigger
Otherwise when we connect to a target that's already halted due to a
trigger, we won't correctly step past it.
Change-Id: I23b9482fa9597af826770f9cebf247b7ba59f65c
* Also disable/reenable triggers around single step.
Gdb is smart enough to disable/step/resume if it set the triggers, but
if a user set them manually it also needs to happen.
Change-Id: I1251bd47199b6f15f61a93e3a521a53f2b677c5f
* Fix whitespace.
Change-Id: Icc240aecbc7e3e36ce4e4d784f5703304334ca13
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions