# Configure the model

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/automotive/zenacssdebug/)
- [Getting started](https://learn.arm.com/learning-paths/automotive/zenacssdebug/zena/)
- [Launch the FVP](https://learn.arm.com/learning-paths/automotive/zenacssdebug/launch/)
- [Configure the model](https://learn.arm.com/learning-paths/automotive/zenacssdebug/config/)
- [Create debug connections](https://learn.arm.com/learning-paths/automotive/zenacssdebug/connect/)
- [Debug RSE from reset](https://learn.arm.com/learning-paths/automotive/zenacssdebug/rse/)
- [Debug Safety Island code](https://learn.arm.com/learning-paths/automotive/zenacssdebug/safetyisland/)
- [Debug primary compute and Linux](https://learn.arm.com/learning-paths/automotive/zenacssdebug/primarycompute/)
- [Next Steps](https://learn.arm.com/learning-paths/automotive/zenacssdebug/_next-steps/)

## Set up a debug configuration for the Zena CSS FVP

Now you’ll walk through setting up an Arm Development Studio debug configuration for the Zena CSS FVP using the Iris interface. This is a fast, reliable path to a working configuration.

As of Arm Development Studio 2025.0, there is no out-of-the-box configuration for the Zena CSS FVP. Creating one, however, is straightforward.

For full guidance, see the Arm Development Studio [Getting Started Guide](https://developer.arm.com/documentation/101469/latest/Migrating-from-DS-5-to-Arm-Development-Studio/Connect-to-new-or-custom-models). A concise, task-focused version is below.

## Launch the FVP (with Iris)

Launch the FVP with the Iris server enabled:

```
kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100"
```

If connecting to the FVP remotely, you can use this command:

```
kas shell -c "../layers/meta-arm/scripts/runfvp -t tmux --verbose -- --iris-server --iris-port 7100 -A"
```

<ads-card>
<ads-card-label>Note</ads-card-label>
<ads-card-content>

This example modeled below uses a local connection for the remaining steps.

</ads-card-content>
</ads-card>

## Create a configuration database in Arm Development Studio

Debug configurations are stored in a configuration database. Create a local database to store your model configuration:

- In Arm Development Studio, go to **File > New > Other**.
- Select **Configuration Database > Configuration Database**.
- Click **Next**, enter a **Name**, then click **Finish**.

## Create a model configuration for Zena CSS FVP (Iris)

- Open the same wizard (**File > New > Other**), then choose **Configuration Database > Model Configuration**.
- Click **Next**, select the **Configuration Database** you created, then click **Next**.
- For **Model Interface**, choose **Iris**, then click **Next**.
- Choose **Browse for model running on local host**. Select your FVP and click **Finish**. The debugger detects and interrogates the FVP.
- If connecting remotely, choose **Connect to model running on either local or remote host** and provide the host and port.

<ads-card>
<ads-card-label>Tip</ads-card-label>
<ads-card-content>

The name of the FVP may be displayed as `RD_ASD` or other.

If unsure, use the port number to identify the correct FVP.

</ads-card-content>
</ads-card>

Arm Development Studio generates a `<code>model.mdf</code>` file that enumerates all CPUs in the FVP.

Optionally, update **Manufacturer Name** (for example, `<code>Arm</code>`) and **Platform Name** (for example, `<code>Zena_CSS_FVP</code>`).

**Save** and **Import** the model into the configuration database.

<ads-card>
<ads-card-label>Tip</ads-card-label>
<ads-card-content>

If the FVP is not detected, verify the Iris server is running on the expected port (`7100` by default) and that your firewall allows local connections.

For remote connections, confirm the host is reachable and the port is open.

</ads-card-content>
</ads-card>

A `<code>model.mdf</code>` file will be created that identifies all CPUs within the FVP.

The debugger is now aware of the FVP and you are ready to debug.