nrf51: verify that UICR needs erasing before triggering an error about it
commit56802d794e9b23c290ccb373c44b86999f35ca20
authorJim Paris <jim@jtan.com>
Wed, 29 Oct 2014 23:00:52 +0000 (29 19:00 -0400)
committerSpencer Oliver <spen@spen-soft.co.uk>
Mon, 24 Nov 2014 21:54:02 +0000 (24 21:54 +0000)
tree9fe06454987b7f35b59f49396e91e4cb129f6641
parentf30bb58644ac604f67837b7a4d7ba22fb77a1974
nrf51: verify that UICR needs erasing before triggering an error about it

If the UICR is already empty, there's no reason to return an error
just because it can't be erased again.  This happens, for example,
when flashing UICR from GDB after a "monitor nrf51 mass_erase".

Change-Id: Ia6d28c43189205fb5a7120b1c7312e45eb32edb7
Signed-off-by: Jim Paris <jim@jtan.com>
Reviewed-on: http://openocd.zylin.com/2363
Tested-by: jenkins
Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
src/flash/nor/nrf51.c