From 49799b827856bd911e6b86821a9ec95687c4ca78 Mon Sep 17 00:00:00 2001 From: Randall Spangler Date: Mon, 8 Jul 2013 11:11:06 -0700 Subject: stm32l: Fix flash_is_erased() detection STM32L erases flash to 0, not 1, so we need a config value to indicate that. This speeds up flash erase on STM32L by not re-erasing already-erased blocks. BUG=chrome-os-partner:13066 BRANCH=none TEST=manual - hack flash_physical_erase() to print something just after flash_is_erased() check. 1. flasherase 0x1f800 0x800 2. flashwrite 0x1fa00 0x100 3. flasherase 0x1f800 0x800 -> only re-erases 0x1fa00 Change-Id: I4d726caf0605e7815b9360bb2d44bdfdd757b4a2 Signed-off-by: Randall Spangler Reviewed-on: https://gerrit.chromium.org/gerrit/61110 Reviewed-by: Bill Richardson --- chip/stm32/config-stm32l15x.h | 3 +++ 1 file changed, 3 insertions(+) (limited to 'chip/stm32/config-stm32l15x.h') diff --git a/chip/stm32/config-stm32l15x.h b/chip/stm32/config-stm32l15x.h index eac9347ecb..c03ff5d8e9 100644 --- a/chip/stm32/config-stm32l15x.h +++ b/chip/stm32/config-stm32l15x.h @@ -36,3 +36,6 @@ /* Lots of RAM, so use bigger UART buffer */ #define CONFIG_UART_TX_BUF_SIZE 2048 + +/* Flash erases to 0, not 1 */ +#define CONFIG_FLASH_ERASED_VALUE32 0 -- cgit v1.2.1