Well... turns out that it may have been a red herring. In my attempts to
debug, bisecting, power cycling, etc., the assert is gone. I am now on
today's master with only your patch *and* the change to at91samdXX.cfg and
everything is working great.

Sorry for the bogus error report.

On Thu, Dec 22, 2016 at 12:24 PM, Paul Fertser <fercer...@gmail.com> wrote:

> Hello Mark,
>
> On Thu, Dec 22, 2016 at 11:41:11AM -0500, Mark Odell wrote:
> > However, there is some change after commit
> > bcaf775fc10d88d2c63c06bafada141895318b34 that causes me to take an
> assert. This
> > happens on the current master with or without your patch. Here's the
> backtrace:
>
> Can you please paste a -d3 log that leads to that?
>
> --
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:fercer...@gmail.com
>
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to