You can launch the FVP within the build environment with the software stack loaded:
kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose"
See the Arm Zena CSS User Guide for further information.
While you can continue to use this method during debugging, it does not enable the Iris debug server in the model, so the system cannot be debugged from Arm Development Studio. Additional command-line options are required.
You will use the following options (see FVP_RD_Aspen --help for the full list). Options are case-sensitive.
| Option | Alias | Notes |
|---|---|---|
--iris-server | -I | Start the Iris debug server |
--iris-port <port> | Set the Iris port (default 7100) | |
--run | -R | Run the simulation when the debug server starts |
--iris-allow-remote | -A | Allow remote connections (only if required) |
Append -- to pass model options through runfvp.
Start the model with the debug server and hold at reset:
kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100"
Start the model with the debug server and begin execution so that boot can progress:
kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100 --run"
If required, allow remote debug connections using option aliases:
kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- -I -A --iris-port 7100"
Even when using the default, specify the Iris port explicitly so it matches your debugger connection settings. If you enable remote connections, ensure your firewall allows inbound access to the chosen port.