> 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/first-steps/integrate-ehs-into-rt-lab-and-hypersim-models/prepare-an-rt-lab-model/view-build-report-and-logs.md).

# View Build Report & Logs

## Overview

Whenever an eHS circuit is processed, the eHS solver generates a **Build Report** and a set of **log files** describing the circuit, solver configuration, firmware resources, and hardware mappings.

These files are valuable for:

* Troubleshooting build and configuration issues.
* Verifying firmware and solver settings.
* Checking FPGA resource usage.
* Reviewing hardware I/O allocations.
* Analyzing eHS and HSCS circuit capacity.
* Understanding how circuits, signals, and measurements are mapped between the CPU and FPGA.

The **Build Report** summarizes the final processed circuit configuration, while the log files provide detailed information about the compilation and validation process.

## Open the Build Report

To open the latest Build Report:

1. Right-click the <code class="expression">page.vars.block\_name</code> block.
2. Select **eHS > Open Build Report**.

The report is opened using the system's default text editor.

### When to consult the Build Report

The **Build Report** is particularly useful when:

* A circuit cannot be built or loaded.
* The selected timestep cannot be achieved.
* FPGA resource limits are reached.
* Hardware I/O mappings need to be verified.
* Solver settings need to be validated.
* HSCS circuits exceed available capacity.

## Build Report sections

### General

Provides information about the software environment and project configuration used to generate the circuit.

Typical information includes:

* eFPGASIM version
* Schematic Editor version
* Unified Database version
* Circuit name
* Selected firmware
* Output directory

### eHS solver

Summarizes the configuration and resource utilization of the eHS solver.

Typical information includes:

* Solver generation
* Effective timestep
* Available timestep range
* Solver strategy
* Resource utilization
* Component counts
* License class information

This section is often the first place to check when optimizing performance or troubleshooting capacity issues.

### HSCS solver

Available when the model contains **High-Speed Converter Solver (HSCS)** circuits.

This section provides:

* HSCS circuit names
* Number of instances
* Effective timestep
* Oversampling settings
* Resource utilization
* Switching capacity usage

Use this section to determine whether HSCS circuits fit within the available firmware capacity.

### I/O connection information

Lists how circuit signals are mapped to hardware resources.

Typical information includes:

* Analog inputs
* Analog outputs
* Digital inputs
* SFP inputs
* SFP outputs
* Encoder outputs

Use this section to verify channel assignments and hardware connectivity.

### Details

Provides low-level information used by the CPU model and FPGA solver.

Typical information includes:

* Source mappings
* Measurement mappings
* High-latency outputs
* Thermal loss gate mappings
* Switch breakdown information

This section is primarily useful for advanced troubleshooting and diagnostics.

### Miscellaneous

Contains additional firmware-specific information and resource allocation details.

Examples include:

* Sine Wave Generator availability
* TSD channel usage
* Measurement routing information

## Open the Log folder

To open the log directory:

1. Right-click the **eHS\_SE\_SFunction\_Drivers** block.
2. Select **eHS > Open Log Folder**.

The log folder contains the Build Report and additional files generated during circuit processing.

### When to consult the log files

Log files are typically used when:

* A build fails.
* Circuit validation detects errors.
* Firmware compatibility issues occur.
* Resource allocation problems are reported.
* Additional troubleshooting information is required beyond what is shown in the Build Report.

For most troubleshooting activities, start with the **Build Report** and consult the **log files** only when more detailed diagnostic information is required.


---

# 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/first-steps/integrate-ehs-into-rt-lab-and-hypersim-models/prepare-an-rt-lab-model/view-build-report-and-logs.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.
