> 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/rt-lab/simulink-blocks-reference/efpgasim-library/opal-rt-schematic-editor-workflow/custom-model-cpu.md).

# Custom Model CPU

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2FyHrd5GrfxnbwTxXgpHeH%2Fimage.png?alt=media&amp;token=069f962a-9bb1-4db2-81f2-03f6e0f467fc" alt="" width="358"><figcaption></figcaption></figure>

The **Custom Model CPU** block, located in the **eFPGAsim** library, enables connectivity to a Custom Model through the CPU/FPGA interfaces defined in the *.ioconf* file associated with the *.bin* file specified in the **OpCtrl** block. It provides an interface for exchanging signals between the application and the **Custom Model XSG** block, allowing signals to be both transmitted to and received from the Custom Model.

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2FGA8Tac0bsVC5MYwuqByS%2Fimage.png?alt=media&amp;token=a72a511d-ecb2-4a3a-8a04-fc0696d54465" alt=""><figcaption></figcaption></figure>

| Parameter             | Description                                                                                                                                                                         |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Controller name**   | Define the OpCtrl controller name to use. The .bin file defined in the OpCtrl block will be the source for the .ioconf the Custom Model block will parse to find XSG Custom Models. |
| **Custom Model name** | Dropdown to choose which XSG custom model block to control. All Custom Models with CPU/FPGA connections in the OpCtrl .bin file will appear in the list.                            |

## Inputs

| Input | Description                                                                                                |
| ----- | ---------------------------------------------------------------------------------------------------------- |
| x     | The block will have as many inputs as are defined in the CPU Inputs textbox of the XSG Custom Model block. |

## Outputs

| Output | Description                                                                                                  |
| ------ | ------------------------------------------------------------------------------------------------------------ |
| x      | The block will have as many outputs as are defined in the CPU Outputs textbox of the XSG Custom Model block. |


---

# 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/rt-lab/simulink-blocks-reference/efpgasim-library/opal-rt-schematic-editor-workflow/custom-model-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.
