diff options
| author | Paul Fertser <fercerpav@gmail.com> | 2015-01-23 12:33:50 +0300 |
|---|---|---|
| committer | Spencer Oliver <spen@spen-soft.co.uk> | 2015-02-04 22:00:52 +0000 |
| commit | cd72808889e426d15c07949c8fcea50dc40fe393 (patch) | |
| tree | f17770d7949a1750ae4ac3ef4c9ea32c0d228489 /src/flash/common.c | |
| parent | c9639ae2acb5554c7b61cda2b4251b4e22223d8b (diff) | |
flash/nor/stm32l: fix mass erase
Topaz reports on http://sourceforge.net/p/openocd/tickets/87/ that
protection level constants are mixed up. This leads to device ending
up in protection level 1 after mass erase.
Additional work is required to actually put the device in RDP Level 1
and then back to Level 0, as Option bootloader launch is a special
kind of full target reset.
To be able to flash properly after mass_erase a "reset init" is needed
(it's anyway recommended to always perform it before any flash
operation).
Change-Id: I9a838909458039bb0114d3019723bf134fa4d7c9
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Reviewed-on: http://openocd.zylin.com/2490
Tested-by: jenkins
Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
Diffstat (limited to 'src/flash/common.c')
0 files changed, 0 insertions, 0 deletions