From: Øyvind Harboe Date: Thu, 29 Apr 2010 01:49:32 +0000 (+0200) Subject: flash: write_image will now pad erase to nearest sector X-Git-Tag: v0.5.0-rc1~734 X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=commitdiff_plain;h=78248f1df67d1b4feefd8ac4e459acd7599d6af2;hp=49b7905cae66ee9e011c71aff758fafba823f87f flash: write_image will now pad erase to nearest sector this is done for unlocking and it is a simple omission that it wasn't done for sectors. The unnerving thing is that nobody has complained about this until now.... Signed-off-by: Øyvind Harboe --- diff --git a/src/flash/nor/core.c b/src/flash/nor/core.c index b8dda96b0f..1ff41937f6 100644 --- a/src/flash/nor/core.c +++ b/src/flash/nor/core.c @@ -1,6 +1,6 @@ /*************************************************************************** * Copyright (C) 2005 by Dominic Rath * - * Copyright (C) 2007,2008 Øyvind Harboe * + * Copyright (C) 2007-2010 Øyvind Harboe * * Copyright (C) 2008 by Spencer Oliver * * Copyright (C) 2009 Zachary T Welch * * * @@ -519,12 +519,6 @@ int flash_write_unlock(struct target *target, struct image *image, struct flash_bank *c; int *padding; - /* REVISIT do_pad should perhaps just be another parameter. - * GDB wouldn't ever need it, since it erases separately. - * But "flash write_image" commands might want that option. - */ - bool do_pad = false; - section = 0; section_offset = 0; @@ -694,7 +688,7 @@ int flash_write_unlock(struct target *target, struct image *image, { /* calculate and erase sectors */ retval = flash_erase_address_range(target, - do_pad, run_address, run_size); + true, run_address, run_size); } }