> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/procedures/amd/projects/common/test-jig-setups/nio-basic-test-jig-setup.md).

# Nio Basic Test Jig Setup

Prepared By Lior Jigalo

<figure><img src="https://1088183085-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJFLva22tpaI24LDZcexP%2Fuploads%2Fx49jbsWZcWV1yKGg7hNw%2Fimage.png?alt=media&amp;token=fb3e3164-0aba-4936-a0c4-cd8c56ba247c" alt=""><figcaption></figcaption></figure>

#### Connecting SX

1. Populate SX card with 2x NVME, WiFi, modem and SIM cards.
2. Connect SX connector to NIO card. Make sure about the following:
   1. SX is laid to the side away from SOM installation.&#x20;
   2. Insulation (like cardboard or a plastic sheet between SX and NIO.

#### NIO panel connectors

3. Connect thumb drive with test image to USB 10G port (lowest one).
4. Connect USB hub to USB 3.2 gen.
   1. Connect Display Jig USB to DUT
   2. Connect the full size display port from Display Jig to DUT.
   3. Connect 2x mini-Display port from Display Jig to DUT.
   4. Connect hdmi from Display Jig to DUT.
   5. Connect mini-USB cable from the USB hub to the console port (loopback).
5. Connect a USB-to-Ethernet adapter to USB 3.2 port and insert LAN cable in adapter.
6. Connect a USB 3.2 gen 2 Thumb drive.&#x20;
7. Ensure DC cable is connected to SOM DC-in connector (do not yet connect PSU).


---

# 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://dev.solid-run.com/procedures/amd/projects/common/test-jig-setups/nio-basic-test-jig-setup.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.
