summaryrefslogtreecommitdiff
path: root/common/flash.c
diff options
context:
space:
mode:
authorStefan Roese <sr@denx.de>2013-04-04 15:53:14 +0200
committerStefan Roese <sr@denx.de>2013-04-22 10:56:38 +0200
commit352ef3f1b613cb711c51ec962d2cc1eafff1bf95 (patch)
tree22778d28cc3a90d6c725e7e254b00d7c0e4a2b8a /common/flash.c
parentd10f68ae47b67acab8b110b5c605dde4197a1820 (diff)
downloadu-boot-imx-352ef3f1b613cb711c51ec962d2cc1eafff1bf95.zip
u-boot-imx-352ef3f1b613cb711c51ec962d2cc1eafff1bf95.tar.gz
u-boot-imx-352ef3f1b613cb711c51ec962d2cc1eafff1bf95.tar.bz2
flash: Add optional verify-after-write feature
Sometimes it might make sense to verify the written data to NOR flash. This patch adds this feature. To enable this verify-after-write, you need to define CONFIG_FLASH_VERIFY in your board config header. Please note that this option is useless in nearly all cases, since such flash programming errors usually are detected earlier while unprotecting/erasing/programming. Please only enable this option if you really know what you are doing. Signed-off-by: Stefan Roese <sr@denx.de>
Diffstat (limited to 'common/flash.c')
-rw-r--r--common/flash.c11
1 files changed, 11 insertions, 0 deletions
diff --git a/common/flash.c b/common/flash.c
index 8244ba2..0c57a3f 100644
--- a/common/flash.c
+++ b/common/flash.c
@@ -149,6 +149,9 @@ flash_write (char *src, ulong addr, ulong cnt)
flash_info_t *info_first = addr2info (addr);
flash_info_t *info_last = addr2info (end );
flash_info_t *info;
+ __maybe_unused char *src_orig = src;
+ __maybe_unused char *addr_orig = (char *)addr;
+ __maybe_unused ulong cnt_orig = cnt;
if (cnt == 0) {
return (ERR_OK);
@@ -185,6 +188,14 @@ flash_write (char *src, ulong addr, ulong cnt)
addr += len;
src += len;
}
+
+#if defined(CONFIG_FLASH_VERIFY)
+ if (memcmp(src_orig, addr_orig, cnt_orig)) {
+ printf("\nVerify failed!\n");
+ return ERR_PROG_ERROR;
+ }
+#endif /* CONFIG_SYS_FLASH_VERIFY_AFTER_WRITE */
+
return (ERR_OK);
#endif /* CONFIG_SPD823TS */
}