diff options
| author | Lieven Hollevoet <lieven@quicksand.be> | 2016-03-25 15:05:35 +0100 |
|---|---|---|
| committer | Freddie Chopin <freddie.chopin@gmail.com> | 2016-05-05 22:55:56 +0100 |
| commit | 241a92d0f2d2ab57d29a665dd34f0000709c13a7 (patch) | |
| tree | 9ff5740420b96f8f45b7f3afbae610aad1c27296 /src/flash/nor/drivers.c | |
| parent | b28c9d32ca4c6b5b9a4a2bfb7784e2a5c13a7632 (diff) | |
Support for debug interface lock of EFM32 controllers
The capability to lock the debug interface on EFM32
controllers was lacking in OpenOCD.
After receiving some pointers by zapb_ and PaulFertser
on IRC (thanks guys!) I have added this capability.
This works by writing the required bits in the debug
lock word to '0'.
Note: there is currently no way to re-enable the debug
interface from OpenOCD as doing this requires specific
pin wiggling that is currently not implemented yet.
However: having the capability to lock the debug interface
is useful when building a volume programming jig.
You can flash the program code, verify and then
lock the debug interface so that the device cannot
be read when it is deployed in the field.
Change-Id: If2d562dfdb4b95519785a4395f755d9ae3d0cf12
Signed-off-by: Lieven Hollevoet <hollie@lika.be>
Reviewed-on: http://openocd.zylin.com/3389
Tested-by: jenkins
Reviewed-by: Freddie Chopin <freddie.chopin@gmail.com>
Diffstat (limited to 'src/flash/nor/drivers.c')
0 files changed, 0 insertions, 0 deletions