summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSandrine Bailleux <sandrine.bailleux@arm.com>2018-02-14 09:34:06 +0100
committerSandrine Bailleux <sandrine.bailleux@arm.com>2018-02-14 09:36:46 +0100
commitd08bc0d1013b6aa939ea1f701ae34e45da8e8246 (patch)
treee6c0b356dc69425db0d500313eec35233eaa8474 /docs
parent0f3947be2406484ab1e056d2a1e7d0c97a21583e (diff)
Disable NVM support by default
Change the default value of the USE_NVM build flag to 0. The idea behind storing test results in NVM was that it makes it possible to retrieve them post-mortem if some TFTF test crashes badly or hangs the board and you have to power it off. But we never got to develop the tooling that enables this use case. Also, when NVM support is enabled, it allows to resume an interrupted test session wherever you left it. At least that's the theory but in practice it seems to have cause more issues than it has helped. Until we make it easy to use the features enabled by USE_NVM=1, we might as well disable NVM support, as this significantly slows tests down. Change-Id: Ib1021cb18a19538e1b004ae6c34d1b6460f0b673 Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/user-guide.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/user-guide.md b/docs/user-guide.md
index df80778..cef80c2 100644
--- a/docs/user-guide.md
+++ b/docs/user-guide.md
@@ -148,7 +148,7 @@ performed.
* `USE_NVM`: Used to select the location of test results. It can take either
0 (RAM) or 1 (Secondary memory like flash) as test results storage. Default
- value is 1.
+ value is 0, as writing to the flash significantly slows tests down.
* `FIRMWARE_UPDATE`: Whether the Firmware Update non-secure images (i.e.
`NS_BL1U` and `NS_BL2U` images) should be built. The default value is 0. The