summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorgcembed <gcembed@gmail.com>2010-06-01 13:48:22 +0200
committerØyvind Harboe <oyvind.harboe@zylin.com>2010-06-03 20:40:00 +0200
commita1cf1b52444c67b6c56ad58fe29be5a285b244cb (patch)
tree7a658f986f40a1ebccfc67865505bc03594f5219 /COPYING
parent631514724db1772f9e08e1dcb564fe9205def57e (diff)
downloadopenocd+libswd-a1cf1b52444c67b6c56ad58fe29be5a285b244cb.tar.gz
openocd+libswd-a1cf1b52444c67b6c56ad58fe29be5a285b244cb.tar.bz2
openocd+libswd-a1cf1b52444c67b6c56ad58fe29be5a285b244cb.tar.xz
openocd+libswd-a1cf1b52444c67b6c56ad58fe29be5a285b244cb.zip
stm32 : change returned value of mass_erase function
Hello, "stm32x mass_erase" return ERROR_OK even if something goes wrong. Here is a summary of changes : * in stm32x_mass_erase : return ERROR_FLASH_OPERATION_FAILED when error detected in FLASH_SR register; * in COMMAND_HANDLER(stm32x_handle_mass_erase_command) : return the returned value of stm32x_mass_erase(). I don't know if there is reason to always return ERROR_OK ? Gaëtan
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions