> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/ehs/3.7/model-in-schematic-editor/manage-firmware-and-simulator-setup.md).

# Manage Firmware & Simulator Setup

The **Firmware Manager** and **Simulator Setup** are used to configure the target hardware, select firmware, and manage available firmware versions. There are two typical workflows:

* [Use a Standard eHS Firmware](https://www.opal-rt.com/docs/ehs/3.7/model-in-schematic-editor/manage-firmware-and-simulator-setup/use-a-standard-ehs-firmware.md)
* [Use a Custom eHS Firmware](https://www.opal-rt.com/docs/ehs/3.7/model-in-schematic-editor/manage-firmware-and-simulator-setup/use-a-custom-ehs-firmware.md)

Detailed instructions for each workflow are provided in their respective sections. This page summarizes the common concepts and tools used in both workflows.

## Simulator Setup

The **Simulator Setup** is used to configure the hardware and firmware associated with an eHS circuit. To open it, navigate to **Simulate** in the Schematic Editor menu bar and select **Simulator Setup**.

A circuit can contain multiple simulator setups, although only one can be active at a time.

Within the Simulator Setup, you can:

* Select the simulator or expansion unit
* Choose the eHS license class
* Select the FPGA firmware
* Review available interfaces and I/O resources
* Configure hardware- and firmware-specific settings

## Firmware Manager

The **Firmware Manager** allows you to view firmware details, import custom firmware, and manage available firmware versions. To open it, navigate to **Simulate** in the Schematic Editor menu bar and select **Firmware Manager**.

The firmware table lists all available firmware, the details panel shows information for the selected firmware, and the footer displays the total number of firmware versions. Select a firmware to view its **name**, **revision**, **platform**, **supported hardware**, and **usage information**.

### Sort firmware

By default, firmware is sorted by name in ascending order. Click a column header to sort by that field, then click again to reverse the sort order.

### Filter firmware

Use the filter field to search firmware by:

* Name
* Revision
* Platform

The filter supports multiple search terms. For example: `kintex 1.2` returns firmware that matches both the specified platform and revision criteria. Filtering and sorting can be combined to quickly locate specific firmware versions.

### Import firmware

Custom firmware must be imported before it can be selected in a **Simulator Setup**. For instructions, see [Use a Custom eHS Firmware](broken://pages/R8xcTcpnVPGBqIWlrjxZ).

### Delete firmware

To remove a firmware version, hover over the firmware entry and click the trash can icon that appears.

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-40df12f4a91495708ac8589f3d6fab5af28acbb8%2FSE_sup_firmware_list.png?alt=media" alt=""><figcaption></figcaption></figure>

If the firmware is currently used by one or more models, a warning is displayed identifying the affected models before confirmation is requested. Deleted firmware can be imported again at any time.

{% hint style="info" %}
Firmware provided by the application database (official firmware) cannot be deleted.
{% endhint %}

To restore the firmware list, click on the recycle-icon button above the firmware table.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/ehs/3.7/model-in-schematic-editor/manage-firmware-and-simulator-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
