From: Paul F. <fer...@gm...> - 2018-02-21 18:53:48
|
On Wed, Feb 21, 2018 at 11:36:36AM +0100, Thomas Doerfler wrote: > I came around a serious problem regarding openOCD 0.10.0, an ATSAME70 > (Cortex M7) board, gdb and breakpoints (incl. single-stepping). As a temporary workaround, you can use "hbreak" in gdb instead of regular "break", that will make it use hardware breakpoints which do not modify RAM. There's also an openocd command that overrides default GDB behaviour so that you can force any breakpoint set by GDB to be a hardware one. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fer...@gm... |