> 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/library-blocks-reference/line-blocks/half-line-fpga-to-cpu.md).

# Half Line FPGA to CPU

## Description

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

The **Half Line FPGA to CPU** block models a decoupling point between the FPGA and CPU by representing both the line parameters and the communication latency. Depending on the selected line type, the corresponding inductance or capacitance must be specified.

{% hint style="info" %}
This block is only available in the eHS library.
{% endhint %}

Each **Half Line FPGA to CPU** block in the Schematic Editor must be paired with a corresponding **Half Line** block in the CPU model. The parameters of both blocks must be configured identically.

* **RT-LAB:** **eFPGASIM Library > External Circuit Editor Workflow > Lines and Loads**
* **HYPERSIM:** **Network Tools**

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

## Parameters

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

| Parameter                                      | Description                                                                                                                | Sets feature | I/O & monitoring |
| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------ | ---------------- |
| **Type**                                       | Conductance type of the half line. Two options: inductive or capacitive.                                                   | No           | N/A              |
| **Inductance L**<sub>**s**</sub>**&#x20;(H)**  | <p><em>Available only when Type is set to Inductive.</em><br>Inductance value of the half line.</p>                        | No           | N/A              |
| **Capacitance C**<sub>**s**</sub>**&#x20;(F)** | <p><em>Available only when Type is set to Capacitive.</em><br>Capacitance value of the half line.</p>                      | No           | N/A              |
| **De-coupling latency (s)**                    | Latency between the FPGA and CPU. When set to **Auto**, eHS automatically estimates a suitable value based on the circuit. | No           | N/A              |

## Conserving ports

| Port   | Description                               |
| ------ | ----------------------------------------- |
| **p1** | Phase terminal on side 1 of the half line |
| **p2** | Phase terminal on side 2 of the half line |


---

# 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/library-blocks-reference/line-blocks/half-line-fpga-to-cpu.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.
