If the bootcounter address is in a cached memory,
a flush of dcache must occur after updateing the bootcounter.

Issue found on i.MX6 where bootcounter is put into the internal
(cached) IRAM.

Signed-off-by: Stefano Babic <sba...@denx.de>
---
 drivers/bootcount/bootcount.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/bootcount/bootcount.c b/drivers/bootcount/bootcount.c
index d5ce450..48594a6 100644
--- a/drivers/bootcount/bootcount.c
+++ b/drivers/bootcount/bootcount.c
@@ -59,6 +59,9 @@ __weak void bootcount_store(ulong a)
        raw_bootcount_store(reg, a);
        raw_bootcount_store(reg + 4, BOOTCOUNT_MAGIC);
 #endif /* defined(CONFIG_SYS_BOOTCOUNT_SINGLEWORD */
+       flush_dcache_range(CONFIG_SYS_BOOTCOUNT_ADDR,
+                               CONFIG_SYS_BOOTCOUNT_ADDR +
+                               CONFIG_SYS_CACHELINE_SIZE);
 }
 
 __weak ulong bootcount_load(void)
-- 
2.7.4

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to