forked from auracaster/openocd
NOR: add FIXMEs for writing ones
It can invalidate ECC codes, and in general is not guaranteed to work. (However on some chips it _appears_ to behave.) Just don't do it; don't write in those cases. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
This commit is contained in:
@@ -449,9 +449,12 @@ int flash_write_unlock(struct target *target, struct image *image,
|
||||
break;
|
||||
}
|
||||
|
||||
/* REVISIT This needlessly touches sectors BETWEEN the
|
||||
/* FIXME This needlessly touches sectors BETWEEN the
|
||||
* sections it's writing. Without auto erase, it just
|
||||
* writes ones; unlikely to destroy data.
|
||||
* writes ones. That WILL INVALIDATE data in cases
|
||||
* like Stellaris Tempest chips, corrupting internal
|
||||
* ECC codes; and at least FreeScale suggests issues
|
||||
* with that approach (in HC11 documentation).
|
||||
*
|
||||
* With auto erase enabled, data in those sectors will
|
||||
* be needlessly destroyed; and some of the limited
|
||||
|
||||
Reference in New Issue
Block a user