On Sun, Jan 18, 2015 at 2:15 PM, Jens Bauer <[email protected]> wrote:
>
> Now, I've adapted the file, and was about to test it.
> But in order to make a test, I'd have to get the chip into this
> 'impossible' behaviour.
> So I wrote a small program, with the __WFI() in a loop, and ... It
> flash-programmed fine, even though I kept trying.
> "Hmm. I'll try the sources I used yesterday." ... Still working - "Argh".
>
If you tried the DBGMCU change first, then that effect remains over OpenOCD
restarts and chip resets. Only a target power off restores it.
>
> After messing around with it for another 10 minutes, I suddenly remembered
> that I did a checkout of patch 2467 and rebuild of OpenOCD, yesterday,
> right before getting recharged.
> I suspect that Paul's patch might could have fixed this issue (indirectly)
> ?
>
By itself, that would be unlikely. But of course, your 2466 change in its
dependencies is highly relevant.
/Andreas
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
