Is there any way to trigger simulation stop from application (hosted client) code on these FVP?
Currently, we're relying on some hacky monitoring "UART" telnet port output to kill the FVP when individual runs complete/crash when executing a suite of tests.
Something a little cleaner/robust would be preferable!
-Andrew
Happily I can answer my own question.
The Core fast-model embedded in the FVP implements semi-hosting support. This can be activated via the