From 9ef6e0ce17a0a5a4ee285c4f9705d79e2fea5183 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Sun, 1 Dec 2013 07:39:20 -0600 Subject: [PATCH] Costmet updates, naming, debug output, README file --- configs/sama5d3x-ek/README.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/configs/sama5d3x-ek/README.txt b/configs/sama5d3x-ek/README.txt index b51e0a705cb..060bbe601b5 100644 --- a/configs/sama5d3x-ek/README.txt +++ b/configs/sama5d3x-ek/README.txt @@ -707,6 +707,18 @@ NAND Support Other file systems are not recommended because only NXFFS can handle bad blocks and only NXFFS performs wear-leveling. + NOTE: NXFFS is very slow. The first time that you start the system, + be prepared for a long wait. I have lots of debug on so I don't know + what the optimized wait will be. But with debug ON, the wait is in + units of hours. + + NOTE: There is another NXFFS related issue: When the FLASH is + fully used, NXFFS will restructure the entire FLASH, the delay to + restructure the entire FLASH will probably be even larger. This + solution in this case is to implement an NXFSS clean-up daemon that + does the job a little-at-a-time so that there is no massive clean-up + when the FLASH becomes full. + Application Configuration -> NSH Library CONFIG_NSH_ARCHINIT=y : Use architecture-specific initialization