interesting
/
riscv-openocd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

flash: fix bug with multiple back-to-back flash chips 

flash programming via flash write_image or gdb load would
produce a bogus error message that the flash chip was to
small.

The solution is to limit the current flash programming
run to the current chip.

Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
This commit is contained in:
Øyvind Harboe 2010-11-15 14:43:16 +01:00
parent 52558354e6
commit 2b546fdc45
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/flash/nor/core.c
View File

@ -654,9 +654,13 @@ int flash_write_unlock(struct target *target, struct image *image,
if (run_address + run_size - 1 > c->base + c->size - 1) if (run_address + run_size - 1 > c->base + c->size - 1)
{ {
LOG_ERROR("The image is too big for the flash"); /* If we have more than one flash chip back to back, then we limit
retval = ERROR_FAIL; * the current write operation to the current chip.
goto done; */
LOG_DEBUG("Truncate flash run size to the current flash chip.");
run_size = c->base + c->size - run_address;
assert(run_size > 0);
} }
/* If we're applying any sector automagic, then pad this /* If we're applying any sector automagic, then pad this