> 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/use-a-standard-ehs-firmware.md).

# Use a Standard eHS Firmware

Standard eHS firmware are provided with eHS and are intended for common hardware and I/O configurations. They can be selected directly from the Schematic Editor firmware database when configuring the simulator setup for an eHS circuit.

Use a standard eHS firmware when your application can be supported by one of the standard firmware configurations. If your project requires a specific FPGA board, I/O mapping, solver configuration, and feature set that is not available in the standard eHS firmware list, a custom firmware will be required.

## Configure a Simulator Setup

To use a standard eHS firmware, you must configure a **Simulator Setup**:

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

1. In Schematic Editor, navigate to **Simulate** in the menu bar and select **Simulator Setup**.
2. Click the **+** **icon** to add a new simulator setup. Multiple setups can be defined, but only one can be active at a time.
3. Select the **simulator or expansion unit** corresponding to your hardware. If your system includes multiple units, a separate simulator setup must be configured for each unit using eHS. For each unit, go to the corresponding eHS instance in <code class="expression">space.vars.cpu\_model\_veristand</code>, launch the Schematic Editor, and repeat the configuration.
4. Next, select the **eHS license class**. This selection filters the available firmware based on your license. Refer to your **System Description Document (SDD)** to identify the recommended **bitstream name** and the associated **eHS license class**. The license class can also be inferred from your software platform license.
5. Locate the settings panel on the right. Under **FPGA Firmware**, click **No firmware selected** to display the list of available firmware. This list includes all standard firmware compatible with the selected hardware platform and license class.
6. Review the list of available firmware. If needed, scroll horizontally to view additional entries. Hover over a firmware to display the corresponding **bitstream file name**, and select the one that matches the recommendation in your SDD.
7. Once selected, the simulator setup is automatically updated to reflect the available interfaces. No additional confirmation or “Apply” action is required. Close the **Simulator Setup** window.


---

# 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/use-a-standard-ehs-firmware.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.
