> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/faq/sdk/what-system-resources-are-required-to-support-a-design-including-the-ndi-fpga-codecs.md).

# What system resources are required to support a design including the NDI FPGA Codecs?

To properly implement the FPGA codecs in the NDI Advanced SDK requires: 

* ARM (or x86) CPU running Linux for the NDI software libraries 
* Shared memory between the CPU and FPGA for communicating the compressed NDI data
* Register access to the FPGA from the CPU 
* Frame buffer memory for the FPGA to store uncompressed video data (does not need to be visible to the CPU)

For these reasons the examples provided all target SoC+FPGA parts from Xilinx and Altera.  Using an SoC+FPGA part is not mandatory, but anything else will require additional development effort and similar system performance (eg: a PCIe link to the FPGA could work well for transferring NDI compressed data and register I/O). 

For more detailed information see [FPGA Projects](/all/developing-with-ndi/advanced-sdk/ndi-advanced-sdk-fpga-example-designs-old/ndi-fpga-reference-design/fpga-projects.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ndi.video/all/faq/sdk/what-system-resources-are-required-to-support-a-design-including-the-ndi-fpga-codecs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.