> 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/simulink-sps-workflow/fpga-64-to-64-interconnect-controller.md).

# FPGA 64-to-64 Interconnect Controller

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2FRt80e6h6LZfr2CH3jtED%2Fimage.png?alt=media&amp;token=4fe12bc8-f4fb-4bbe-8ffa-7bd0c7718879" alt=""><figcaption></figcaption></figure>

The  **FPGA 64-to-64 Interconnect Controller** block, located in the **cpuhilios\_lib** library, is used to control an FPGA 64-to-64 Interconnect block used to set dynamically the signal interconnections on FPGA. It should be connected to an FPGA 64-to-64 Interconnect Control Panel that will set this interconnection information according to the selected pattern.

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2FvrNI7FZxhCaceSMFflbB%2Fimage.png?alt=media&amp;token=4058b138-37da-4ee9-a56d-2b22f7101cad" alt=""><figcaption></figcaption></figure>

| Parameter                                              | Description                                                                                                                                                                                             |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Controller Name**                                    | Bind this block to an OpCtrl block by entering the same 'Controller Name' as specified in the OpCtrl block The OpCtrl block controls initialization of the settings of one specific FPGA in the system. |
| **LoadIn port number for interconnection information** | Enter the number of the LoadIn port used to communicate the interconnection information for this block, in the range \[1:32].                                                                           |

## Inputs

| Input       | Description                                                                                                                                       |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **XC\_Cfg** | This signal contains the interconnection information. It should be connected to the output of a "FPGA 64-to-64 Interconnect Control Panel" block. |

## Outputs

This block has no output.

## Characteristics and limitations

| Direct Feedthrough   | NO  |
| -------------------- | --- |
| Discrete sample time | YES |
| XHP support          | YES |
| Work offline         | N/A |


---

# 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/simulink-sps-workflow/fpga-64-to-64-interconnect-controller.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.
