fix: specify FVP start ports explicitly
This change ensures that every supported FVP is explicit about the ports
that it will try to bind to. This is a mitigation against the
sometimes-random order in which terminals are enumerated by the various
FVPs, which causes our LAVA tests to attempt to read from the wrong
terminal.
Signed-off-by: Chris Kay <chris.kay@arm.com>
Change-Id: Ida12fcdae988fe119226c05032c90387e574727b
(cherry picked from commit 30120b38df617c05307ee42f46bc6f5db5d7f568)
diff --git a/model/morello.sh b/model/morello.sh
index 7933f0a..c68c540 100644
--- a/model/morello.sh
+++ b/model/morello.sh
@@ -9,6 +9,14 @@
set_model_path "$warehouse/SysGen/SubSystemModels/$model_version/$model_build/models/$model_flavour/FVP_Morello"
cat <<EOF >"$model_param_file"
+-C board.terminal_uart0_board.start_port=5000
+-C board.terminal_uart1_board.start_port=5001
+-C css.mcp.terminal_uart0.start_port=5002
+-C css.mcp.terminal_uart1.start_port=5003
+-C css.scp.terminal_uart_aon.start_port=5004
+-C css.terminal_uart1_ap.start_port=5005
+-C css.terminal_uart_ap.start_port=5006
+
--data Morello_Top.css.scp.armcortexm7ct=$scp_rom_bin@0x0
--data Morello_Top.css.mcp.armcortexm7ct=$mcp_rom_bin@0x0
-C Morello_Top.soc.scp_qspi_loader.fname=$scp_fw_bin