This lets the user set an itrigger trigger, which doesn't fit in the normal breakpoint abstraction. This implementation only allows control of a single itrigger. Hardware could support more than one, and that may be useful to catch different interrupts in different execution modes. But it would make the code/UI more complex and it feels like an unlikely use case. Change-Id: I76c88636ee73d4bd298b2bd1435cb5d052e86c91 Signed-off-by: Tim Newsome <tim@sifive.com> |
||
---|---|---|
.. | ||
manual | ||
.gitattributes | ||
Makefile.am | ||
fdl.texi | ||
openocd.1 | ||
openocd.texi |