I have added the configuration and I'm testing OpenOCD with an SAM4SA16C chip.
The programming seems to work, but there's some problem with the lock bits.
Executing `flash protect 0 0 127 on` causes only lock bits 0...31 to be set
according to `flash info 0` result. On further investigation it seems that lock
bits 96...127 for `flash protect` are mapped to lock bits 0...31 for `flash
info`.
Could somebody test the current OpenOCD with another SAM4(S) chip?
---
** [tickets:#82] Add flash configuration for Atmel at91sam4sa16 processors**
**Status:** new
**Milestone:** 0.9.0
**Created:** Wed Nov 12, 2014 06:16 PM UTC by Gábor Török
**Last Updated:** Wed Nov 12, 2014 06:17 PM UTC
**Owner:** nobody
Add flash configuration for at91sam4sa16* processors.
---
Sent from sourceforge.net because openocd-devel@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/openocd/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
