Re: [OpenOCD-devel] bypassing reading DAP ID code in SWD init sequence?

2014-08-27 Thread Andrey Yurovsky
On Wed, Aug 27, 2014 at 9:33 AM, Andreas Fritiofson wrote: > > On Mon, Aug 25, 2014 at 7:37 PM, Andrey Yurovsky wrote: >> >> >> Is there a reasonable way to pass something in from the users' config >> file that would then tell the SWD layer to do a fake init (assume the >> expected DAP ID, etc) a

Re: [OpenOCD-devel] bypassing reading DAP ID code in SWD init sequence?

2014-08-27 Thread Andreas Fritiofson
On Mon, Aug 25, 2014 at 7:37 PM, Andrey Yurovsky wrote: > > Is there a reasonable way to pass something in from the users' config > file that would then tell the SWD layer to do a fake init (assume the > expected DAP ID, etc) and set things up so that at least register > writes are possible? If

[OpenOCD-devel] bypassing reading DAP ID code in SWD init sequence?

2014-08-25 Thread Andrey Yurovsky
I've implemented "securing" the Flash on the Atmel SAMD20 (and related parts) which in itself is quite simple. To un-secure it, one must issue a chip erase via the DSU register banks (which was also very simple), however I'm unable to do this in openocd once the device is secured. The reason is t