summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChandni Cherukuri <chandni.cherukuri@arm.com>2018-02-07 09:48:39 +0530
committerThomas Panakamattam Abraham <thomas.abraham@arm.com>2018-02-13 13:38:37 +0000
commit0f3947be2406484ab1e056d2a1e7d0c97a21583e (patch)
treefca4d69a6c11edbdc25557bda787aa6d0c57ca05
parent6febe734d0485015b457238fcb7b197c6bf65b6e (diff)
mem_protect_check: fix the value of MAX_ADDR macro
The MAX_ADDR macro is incorrectly defined as DRAM_SIZE + MAX_SIZE instead of DRAM_BASE + MAX_SIZE. This results in failures for the mem_protect_check test cases which use MAX_ADDR as the base address. So fix the incorrect definition of the MAX_ADDR macro. Change-Id: I3102b06efb66ffa5313b9f48f7eef9ec6fd90dc1 Signed-off-by: Chandni Cherukuri <chandni.cherukuri@arm.com>
-rw-r--r--tests/runtime_services/standard_service/psci/api_tests/mem_protect_check/mem_protect_check.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/runtime_services/standard_service/psci/api_tests/mem_protect_check/mem_protect_check.c b/tests/runtime_services/standard_service/psci/api_tests/mem_protect_check/mem_protect_check.c
index fd78e67..e52d639 100644
--- a/tests/runtime_services/standard_service/psci/api_tests/mem_protect_check/mem_protect_check.c
+++ b/tests/runtime_services/standard_service/psci/api_tests/mem_protect_check/mem_protect_check.c
@@ -38,7 +38,7 @@
*/
#define SECURE_CARVEOUT_SIZE DRAM_TZ_SIZE
#define MAX_SIZE (DRAM_SIZE - SECURE_CARVEOUT_SIZE)
-#define MAX_ADDR (DRAM_SIZE + MAX_SIZE)
+#define MAX_ADDR (DRAM_BASE + MAX_SIZE)
/*
* Test to verify that mem_protect_check_range returns correct answer