From 35260aa0e6fb0f086391404bb9c36f86c2a5e459 Mon Sep 17 00:00:00 2001 From: armink Date: Tue, 25 Oct 2016 23:11:55 +0800 Subject: [PATCH] =?UTF-8?q?1=E3=80=81=E3=80=90=E5=AE=8C=E5=96=84=E3=80=91?= =?UTF-8?q?=E4=B8=80=E5=A4=84=E6=B3=A8=E9=87=8A=E8=AF=B4=E6=98=8E=E3=80=82?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: armink --- easyflash/src/easyflash.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/easyflash/src/easyflash.c b/easyflash/src/easyflash.c index 7e304da..0f6f1aa 100644 --- a/easyflash/src/easyflash.c +++ b/easyflash/src/easyflash.c @@ -46,12 +46,11 @@ * 1.Normal mode: no more limitations * 2.Wear leveling mode: system section will used an flash section and the data section will used at least 2 flash sections * 3.Power fail safeguard mode: ENV area will has an backup. It is twice as normal mode. - * 4.wear leveling and power fail safeguard mode: The system section will used an flash section. - * The data section is twice as wear leveling mode data section size. + * 4.wear leveling and power fail safeguard mode: The required capacity will be 2 times the total capacity in wear leveling mode. * For example: * The EF_ERASE_MIN_SIZE is 128K and the ENV_USER_SETTING_SIZE: 2K. The ENV_AREA_SIZE in different mode you can define * 1.Normal mode: 1*EF_ERASE_MIN_SIZE - * 2.Wear leveling mode: 3*EF_ERASE_MIN_SIZE (It has 2 flash section to store ENV. So ENV can erase at least 200,000 times) + * 2.Wear leveling mode: 3*EF_ERASE_MIN_SIZE (It has 2 data section to store ENV. So ENV can erase at least 200,000 times) * 3.Power fail safeguard mode: 2*EF_ERASE_MIN_SIZE * 4.Wear leveling and power fail safeguard mode: 6*EF_ERASE_MIN_SIZE * @note the log area size must be more than twice of EF_ERASE_MIN_SIZE