run_config: use an associative array to hold fvp container params
The proposed approach uses a associative array to hold all FVP
container parameters: 1. docker image (containing the FVP model)
2. model's absolute path and 3. model binary filename, allowing a single
table to store this infomation instead of multiple run configurations.
It is important to notice that not all models have the corresponding
FVP container (those models with tree semicolon as values,
[XXX]=";;;") because these are not publicly available. The Trusted
Firmware Open CI team (Linaro) will continue this work and get a NDA,
so LAVA testing can enabled on these.
Signed-off-by: Leonardo Sandoval <leonardo.sandoval@linaro.org>
Change-Id: I88913ffbdd22e26f978ce326de0140b4c0eb83d4
diff --git a/run_config/fvp-aemv8a.el3payload b/run_config/fvp-aemv8a.el3payload
index 9f2d68f..c353092 100644
--- a/run_config/fvp-aemv8a.el3payload
+++ b/run_config/fvp-aemv8a.el3payload
@@ -6,11 +6,11 @@
#
post_fetch_tf_resource() {
+ local model="base-aemv8a"
+
pctl_startup="0.0.*.0,0.1.*.0" \
secure_ram_fill="1" \
- model="base-aemv8a" gen_model_params
+ model="$model" gen_model_params
- model="base-aemv8a" \
- model_bin="FVP_Base_AEMv8A-AEMv8A" \
- gen_fvp_yaml
+ model="$model" gen_fvp_yaml
}